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
We are trying to move all our meshes to git repository with LFS support. Currenly the idea to have, for example pi mesh (new version) available by simply:
However in the intake catalog I see that the mesh is present as well (as a zip file). Do you think it would be easier just to include the mesh together with the data, or check it out separatelly from gitlab repo? On the one hand it make sence to include the exact mesh the data were generate with, on the other - one can just provide git hash for the mesh and be sure the right version will be downloaded, and that's something that is stored in one place, and information on meshes is not dublicated.
What do you think is the best way forward?
The text was updated successfully, but these errors were encountered:
We are trying to move all our meshes to git repository with LFS support. Currenly the idea to have, for example pi mesh (new version) available by simply:
I also have generated one year of output with this mesh and put them on Zenodo: https://doi.org/10.5281/zenodo.4109106
However in the intake catalog I see that the mesh is present as well (as a zip file). Do you think it would be easier just to include the mesh together with the data, or check it out separatelly from gitlab repo? On the one hand it make sence to include the exact mesh the data were generate with, on the other - one can just provide git hash for the mesh and be sure the right version will be downloaded, and that's something that is stored in one place, and information on meshes is not dublicated.
What do you think is the best way forward?
The text was updated successfully, but these errors were encountered: