Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[guide] handling ARCs across clones / machines #282

Open
Brilator opened this issue Oct 13, 2023 · 1 comment
Open

[guide] handling ARCs across clones / machines #282

Brilator opened this issue Oct 13, 2023 · 1 comment
Assignees
Labels
content Issues that require an addition or adaption of content

Comments

@Brilator
Copy link
Member

Handling ARCs across machines (laptop, desktop, server, hpc, etc.) is not intuitive.

We need a practical guide / recommendation, e.g.:

  1. DataHUB as "original" clone with all data
  2. Laptop / desktop for small data, to create the ARC, for structuring and metadata annotation, creating scripts, etc.
  3. Clone to server / HPC (ideally via git) where large data is stored for computations
  • Needs to include work with LFS, git / ARC commander handling.
  • Reminders about arc syncing (keep clones up-to-date)
  • notes on working with branches
@Brilator Brilator added the content Issues that require an addition or adaption of content label Oct 13, 2023
@Brilator Brilator self-assigned this Nov 24, 2023
@micwij
Copy link

micwij commented Dec 12, 2023

I think the above are a great basis for recommendations!
I have worked on an ARC across machines and as suggested using git pull worked well to pull the changes made on the respective other machine, so this could also be a good general recommendation to use regularly.

However, this was before I added the raw data to the ARC. Now I am wondering how to e.g. synchronize my laptop without pulling all those large files. If we find a solution, this would also be an important recommendation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issues that require an addition or adaption of content
Projects
None yet
Development

No branches or pull requests

2 participants