Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ideas for new features of the utrwrapper #31

Open
j-kleemann-old opened this issue Aug 20, 2019 · 0 comments
Open

Ideas for new features of the utrwrapper #31

j-kleemann-old opened this issue Aug 20, 2019 · 0 comments

Comments

@j-kleemann-old
Copy link
Collaborator

j-kleemann-old commented Aug 20, 2019

This issue collects ideas on how to improve the utrwrapper

  • The utrwrapper could create hashes of all outputfiles at its final stage to allow for later verification of the integrity of the outputfiles from the belonging logfile

  • The utrwrapper could log the git revision and git status (or create hashes of all source code files) to allow for retracing the status of utr used for the simulation later)

  • The utrwrapper could include an option to perform a functionality as implemented by the fep_efficiency.sh script.

  • The utrwrapper could include an option to just process already done simulations, skipping the actual simulation (in case of processOutput was disabled, but later one one wants it processed in the automatic way) Implemented in b060509

  • The utrwrapper could support a filenameMidfix environment variable also used for globbing. Of pre-, mid- and postfix only one should be mandatory

  • The utrwrapper could replace placeholders in filenamePre-, mid- and postfix trough respective values in the environment variables (e.g. prefix=150Sm_AngDist_{energy}_keV or postfix=_MeV_n={beamOnStatistics})

  • The utrwrapper-angdist-example has as #setterCmd=/ang/delta12 {loopVar} but this should be /ang/delta23 Fixed in 26ce26d

  • The utrwrapper could include an option to disable the check whether its run in an tmux or screen session Implemented as config option 26ce26d

  • The utrwrapper should impose an upper limit on the logfile size: In a worst case scenario a problem can generate tons of output, which can blow up the logfile to gigabytes rapidly (e.g. "Warning: AngularDistributionGenerator: Monte-Carlo method could not determine a starting velocity vector after 10000 iterations" being output many times a second).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant