Changes between Version 15 and Version 16 of WebValidation

Timestamp:

Jun 23, 2010, 12:08:32 AM (14 years ago)

Author:

Neil Christensen

Comment:

--

WebValidation

@@ -15 +15 @@
       * Run CH & MG on resulting code.
       * Each of these condor jobs relies on previous ones.  If a necessary previous step fails, then the next job is not run.  This is controlled by a "DAG" script.
+   * User can choose "stock" models.  There are 2 choices:
+      * Precompiled models that ship with the MEG can be chosen from drop down menu.
+      * User can upload their own "stock" model, but this is harder.
+      * User must also upload "particle translation" file.
+      * User can upload 1 or more parameter files.
+      * Site tests that particle translation file and parameter files work.
+      * If tests passed, then this model can be used in validations.
     * If 1 or more MEG passes, the user is allowed to run 2->2 cs processes.  
       * They can choose the MEG they want to test (among the ones that pass the previous tests).
@@ -22 +29 @@
         * User can restrict on indices and charges.
     * After processes are generated, user can run them.  
+      * User can choose from restrictions and parameters.
+      * User can choose which MEGs to run.
+      * User can choose which "stock" models to run (and which parameter files for them.)
       * The processes are run on Condor.
         * Currently 4 parallel nodes.  Seems pretty fast.
-        * Adds 10 processes to the queue at a time.  This allows multiple users and validations to be run at the same time and make progress at the same time.
+        * Adds 10 jobs to the queue at a time.  Each job has ~5 processes.  This allows multiple users and validations to be run at the same time and make progress at the same time.
         * User can refresh their browser to see the progress.  Each process and MEG that is finished will show up as they are finished.
-      * User can rerun processes.
+      * User can rerun processes choosing new MEG's and new stock models if they like.
     * User can create multiple validations.
     * Multiple validations can be run concurrently.  Condor handles this.
@@ -32 +42 @@
     * Users can delete models.  (But only when no condor jobs are running for this model.)
     * Users can delete validations.  (But only when this validation is not being run.)
+    * Users can delete stock models.
     * Security:
         * All user code is run on condor jobs and no where else.
@@ -38 +49 @@
         * Users do not control condor.  They can only use web form to start jobs and see the outcome.
   * ''To-do'' (for this summer): 
-    * Get FR-SH and FR-WO working.  (Christian Speckner is helping with WO).  This shouldn't be difficult.  The scaffolding is there.
+    * Get FR-SH and FR-WO working.  (WO almost done.).  This shouldn't be difficult.  The scaffolding is there.
     * Test whether a Mathematica license is available.  If not, wait and try again.
-    * Use parameter files in tests.
-    * Allow upload and comparison with "stock" versions of models.
-    * Improve security:
-      * Test that nothing can be written outside of condor job dir.
-      * Test that condor job cannot do any network connections _except_ certain database updates.
-      * Control time, memory and disk space available to condor jobs (admin side).
-      * Only allow transfer back of certain files.  Don't let user overwrite important files...
+  * ''To-do'' (not gauranteed for this summer but hopefully by summer of 2011):
     * Versions of all software used (partly done).
-  * ''To-do'' (not gauranteed for this summer but hopefully by summer of 2011):
     * Add links moving around model database.
     * Add history (if model changes, then keep the old model with versioning.  Do the same for validations, etc..)
@@ -74 +78 @@
       * Add {{{find /var/tmp/. /tmp/. -user $USER | xargs rm -rf}}} to scripts?
       * Test that the web forms do not allow the user to perform any nasty actions (no user commands should be performed.)
+      * Test that nothing can be written outside of condor job dir.
+      * Test that condor job cannot do any network connections _except_ certain database updates.
+      * Control time, memory and disk space available to condor jobs (admin side).
+      * Only allow transfer back of certain files.  Don't let user overwrite important files...
     * Add admin pages for...