search

momentoscope / hextof-processor

Code for preprocessing data from the HEXTOF instrument at FLASH, DESY in Hamburg (DE)
https://hextof-processor.readthedocs.io/en/latest/
GNU General Public License v3.0
7 stars 4 forks source link

Feature/lfs #57

Closed zain-sohail closed 3 years ago

zain-sohail commented 3 years ago

Used Git LFS to migrate already commited .h5 files to lfs using following command in main directory: git lfs migrate import --no-rewrite -m "Import .h5 files to lfs" tutorial/raw/online-0/fl1user2/*.h5

For new files, the .gitattributes contains an attribute that would automatically migrate the h5 files to lfs. Any new file extension or files can be tracked using: git lfs track "<file_ext>"

RealPolitiX commented 3 years ago

Does this affect the way these files are called? If so, please write something in the online documentation, otherwise you can simply merge.

zain-sohail commented 3 years ago

It doesn't. Git LFS creates a pointer file in the repository pointing to the LFS server but the file names stay the same.

RealPolitiX commented 3 years ago

Thanks. My impression is that now they are not copied every time you upload a commit, right? Are there caveats for making new commits now? If not, please merge into the main branch when possible.

zain-sohail commented 3 years ago

Thanks. My impression is that now they are not copied every time you upload a commit, right? Are there caveats for making new commits now? If not, please merge into the main branch when possible.

If you add a new .h5 file and commit it, the file will just become a pointer inside Git, while it stores the contents on remote Github server. Any new .h5 file will automatically go through that procedure since .gitattributes has that defined. We can also add other extensions or subfolders.