You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if you're already aware of this, but there is a package called experi which aims to provide some related functionality to this package.
Experi uses a yaml file to specify different combinations of options for and experiment which scans over various parameters, then helps you submit those as separate simulation jobs in different directories. What would be awesome is if experiment was able to read those same yaml files in to specify the different cases. Then you could use experi to automatically submit the jobs, and experiment to automatically analyse them, while keeping a global record of the options chosen for each case. It's almost like the two packages have tried to implement two halves of the same workflow...
A lot of the internal logic for parsing the yaml files is similar, so you might be interested in that too. I'm not sure how hard this might be to implement, but maybe it's possible to have an alternative yaml parser in experiment which can read the type of files which experi produces? I don't think merging the two packages would make sense because experi is more general in that it doesn't use xarray at all, and experiment is possibly more flexible with its file structures than experi, but explicit support between the two could be great.
I think experi is in an earlier stage of development than experiment, but I just thought I would bring this to your attention.
Let me (and experi's developer @malramsay64) know what you think!
The text was updated successfully, but these errors were encountered:
Thanks for letting me know about experi - it looks really great!
I had originally built this tool for work during my dissertation/post-doc, but it's mostly deprecated at this point - I don't plan on any active development in the future, and really I keep it published here on github for others to check out and as a reference for myself. You're more than welcome to fork and liberally borrow from the code here if there's functionality you would like to have! I licensed under a permissive MIT license, so I would really encourage you to do so, and maybe just mention that some of my work was a helpful reference for your own if you ever publish anything using your package :)
Apologies if you're already aware of this, but there is a package called experi which aims to provide some related functionality to this package.
Experi uses a yaml file to specify different combinations of options for and experiment which scans over various parameters, then helps you submit those as separate simulation jobs in different directories. What would be awesome is if
experiment
was able to read those same yaml files in to specify the different cases. Then you could useexperi
to automatically submit the jobs, andexperiment
to automatically analyse them, while keeping a global record of the options chosen for each case. It's almost like the two packages have tried to implement two halves of the same workflow...A lot of the internal logic for parsing the yaml files is similar, so you might be interested in that too. I'm not sure how hard this might be to implement, but maybe it's possible to have an alternative yaml parser in
experiment
which can read the type of files which experi produces? I don't think merging the two packages would make sense becauseexperi
is more general in that it doesn't use xarray at all, andexperiment
is possibly more flexible with its file structures thanexperi
, but explicit support between the two could be great.I think
experi
is in an earlier stage of development thanexperiment
, but I just thought I would bring this to your attention.Let me (and experi's developer @malramsay64) know what you think!
The text was updated successfully, but these errors were encountered: