Hi Edward.
How much memory would be required to always store the output from the relax
controller ?
Then if an error is occured, the controller log could be dumped to a file
with a timestamp, and comprresed?
In the auto analysises, a call to dump the controller log could also be
done.
Just to make sure, that logs are always preserved.
I know, that they can be of severe size, 50 MB?, ?
Best
Troels
2014-11-20 11:44 GMT+01:00 Edward d'Auvergne <edward@xxxxxxxxxxxxx>:
Hi,
Just so you know, due to the fix for bug #22961
(https://gna.org/bugs/?22961), the failure of relaxation data loading
with the message "IndexError: list index out of range", I plan on soon
release a new relax version with this fix. I don't know why relax
users have not reported this problem before, as it is likely to have
been encountered a few times.
Maybe the solution would be to catch all errors, skip the RelaxErrors
so they proceed as normal, and then create a system for automatic bug
submission? This would be a radical and highly disruptive change
though. A different solution would be required for each UI (prompt,
script, and graphical).
The hard part would be to interface with the Gna! infrastructure.
This may make automation impossible. Therefore maybe a set of
instructions for bug submission should be presented to the user. Some
ideas for the text would be:
- "An unidentified error has been encountered."
- Please create a bug report using the link
https://gna.org/bugs/?func=additem&group=relax.
- Copy and paste the entirety of the error message.
- Attach the log file if one was created (or copy and paste the relax
output or rerun relax with the --log or --tee option), compressing if
it is a large file.
- Ideally create truncated input data files for 1 or 2 spins, slightly
randomising the data and changing file names for privacy, and attach
those files.
- Attach a script file, if it exists.
- If the attached data and script files are sufficient to reproduce
the bug, a solution can usually be found within 5 to 10 minutes.
- Run 'relax --info --tee relax_info.log' and attach the
relax_info.log file to the report.
These are just some ideas for the future.
Regards,
Edward
_______________________________________________
relax (http://www.nmr-relax.com)
This is the relax-devel mailing list
relax-devel@xxxxxxx
To unsubscribe from this list, get a password
reminder, or change your subscription options,
visit the list information page at
https://mail.gna.org/listinfo/relax-devel
Re: Quick release of relax version 3.3.3, and an idea for automatic bug submission when relax crashes.