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
All the experiment results should go to /var/log/hyperboss.log but we have to make sure that there is also some kind of safety mechanism against that file being over written for example with new install or similar situation. There should be no risk of it growing too big, and if it does, we can think about it more then. For now I guess the key point is that there should be an identifier in addition to the hyperscan outputs in terms of what experiment each sample is related with. So maybe add a human readable "experiment id". Perhaps it's a good idea to require the user to input an experiment name when starting hyperboss, and also have a unique id in form of epoch time.
The text was updated successfully, but these errors were encountered:
All the experiment results should go to /var/log/hyperboss.log but we have to make sure that there is also some kind of safety mechanism against that file being over written for example with new install or similar situation. There should be no risk of it growing too big, and if it does, we can think about it more then. For now I guess the key point is that there should be an identifier in addition to the hyperscan outputs in terms of what experiment each sample is related with. So maybe add a human readable "experiment id". Perhaps it's a good idea to require the user to input an experiment name when starting hyperboss, and also have a unique id in form of epoch time.
The text was updated successfully, but these errors were encountered: