[ET Trac] [Einstein Toolkit] #52: Ensure consistency between configurations on different systems

[Einstein Toolkit]

#52: Ensure consistency between configurations on different systems
--------------------------+-------------------------------------------------
  Reporter:  anonymous    |       Owner:  mthomas
      Type:  enhancement  |      Status:  new    
  Priority:  minor        |   Milestone:         
 Component:  SimFactory   |     Version:         
Resolution:               |    Keywords:         
--------------------------+-------------------------------------------------

Comment (by eschnett):

 One of Simfactory's goals is to remove the difference between different
 machines. Ideally, one would just "submit" a simulation, and some semi-
 automated mechanism would figure out where to submit (or would submit
 multiple times and keep only the first job that then starts), or would
 allow easily to restart on a different system, allows monitoring all
 current simulations independent of where they are running, etc.

 I have two thorn lists (development and production) in two different
 source trees, and use the same thorn lists on all systems. If a thorn
 doesn't work on a particular system this is noted in the MDB. I almost
 never specify a configuration name manually. If the default changed from
 "sim" to the thorn list name, I would not be bothered much.

 In a way, this ticket is already implemented. Simfactory distributes e.g.
 the manifest directory, and one can set a default thorn list in
 defs.local.ini.

 Are there people who regularly build multiple configurations in the same
 source tree?

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/52#comment:2>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit