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
Previous benchmark have been hand made and stored - leading to some forgetfulness.
We need to be able to store them properly and draft a website/report that is very detailed and serve as base of truth. Nebulae wiki is one version controlled storage, for example.
We should also archive the results as long as they are compressed to a manageable size (.json of dycore timings, log of GEOS, data in general)
Document workflow (and do required setup) for benchmark data/result save
The text was updated successfully, but these errors were encountered:
FlorianDeconinck
changed the title
Define an archiving mechanism and baselining
[GEOS] Define an archiving mechanism and baselining
May 22, 2024
Previous benchmark have been hand made and stored - leading to some forgetfulness.
We need to be able to store them properly and draft a website/report that is very detailed and serve as base of truth. Nebulae wiki is one version controlled storage, for example.
We should also archive the results as long as they are compressed to a manageable size (.json of dycore timings, log of GEOS, data in general)
The text was updated successfully, but these errors were encountered: