.gitignore

[szabgab]

After running some code I see this:

$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	deleted:    Example/coarse/seq1/output/Traj/Traj_seq1_0.3_333508.dat.bz2
	deleted:    Example/coarse/seq1/output/Traj/Traj_seq1_0.3_463782.dat.bz2
	deleted:    Example/coarse/seq2/output/Traj/Traj_seq2_0.3_269719.dat.bz2
	deleted:    Example/coarse/seq2/output/Traj/Traj_seq2_0.3_788090.dat.bz2
	deleted:    Example/coarse/seq3/output/Traj/Traj_seq3_0.3_813364.dat.bz2
	deleted:    Example/coarse/seq3/output/Traj/Traj_seq3_0.3_872208.dat.bz2
	modified:   scripts/simuAnalysis.py

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	Example/coarse/seq1/output/Traj/Traj_seq1_0.3_333508.dat
	Example/coarse/seq1/output/Traj/Traj_seq1_0.3_333508.pdb
	Example/coarse/seq1/output/Traj/Traj_seq1_0.3_463782.dat
	Example/coarse/seq1/output/Traj/Traj_seq1_0.3_463782.pdb
	Example/coarse/seq2/output/Traj/Traj_seq2_0.3_269719.dat
	Example/coarse/seq2/output/Traj/Traj_seq2_0.3_269719.pdb
	Example/coarse/seq2/output/Traj/Traj_seq2_0.3_788090.dat
	Example/coarse/seq2/output/Traj/Traj_seq2_0.3_788090.pdb
	Example/coarse/seq3/output/Traj/Traj_seq3_0.3_813364.dat
	Example/coarse/seq3/output/Traj/Traj_seq3_0.3_813364.pdb
	Example/coarse/seq3/output/Traj/Traj_seq3_0.3_872208.dat
	Example/coarse/seq3/output/Traj/Traj_seq3_0.3_872208.pdb
	newPathcoarse/

no changes added to commit (use "git add" and/or "git commit -a")

It would be probably better not to delete file while the program is running and put the name of the generated files in .gitignore so they won't show up in git status

Maybe like this:

*.dat
*.pdb

[dorigabay]

yes, but the thing is that those files were generated as an example. In the real real use I would like those files to be deleted since they are taking hard disk space (real simulations files can be tens of GB)

…

On Wed, 2 Mar 2022 at 07:55, Gabor Szabo ***@***.***> wrote: After running some code I see this: $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) deleted: Example/coarse/seq1/output/Traj/Traj_seq1_0.3_333508.dat.bz2 deleted: Example/coarse/seq1/output/Traj/Traj_seq1_0.3_463782.dat.bz2 deleted: Example/coarse/seq2/output/Traj/Traj_seq2_0.3_269719.dat.bz2 deleted: Example/coarse/seq2/output/Traj/Traj_seq2_0.3_788090.dat.bz2 deleted: Example/coarse/seq3/output/Traj/Traj_seq3_0.3_813364.dat.bz2 deleted: Example/coarse/seq3/output/Traj/Traj_seq3_0.3_872208.dat.bz2 modified: scripts/simuAnalysis.py Untracked files: (use "git add <file>..." to include in what will be committed) Example/coarse/seq1/output/Traj/Traj_seq1_0.3_333508.dat Example/coarse/seq1/output/Traj/Traj_seq1_0.3_333508.pdb Example/coarse/seq1/output/Traj/Traj_seq1_0.3_463782.dat Example/coarse/seq1/output/Traj/Traj_seq1_0.3_463782.pdb Example/coarse/seq2/output/Traj/Traj_seq2_0.3_269719.dat Example/coarse/seq2/output/Traj/Traj_seq2_0.3_269719.pdb Example/coarse/seq2/output/Traj/Traj_seq2_0.3_788090.dat Example/coarse/seq2/output/Traj/Traj_seq2_0.3_788090.pdb Example/coarse/seq3/output/Traj/Traj_seq3_0.3_813364.dat Example/coarse/seq3/output/Traj/Traj_seq3_0.3_813364.pdb Example/coarse/seq3/output/Traj/Traj_seq3_0.3_872208.dat Example/coarse/seq3/output/Traj/Traj_seq3_0.3_872208.pdb newPathcoarse/ no changes added to commit (use "git add" and/or "git commit -a") It would be probably better not to delete file while the program is running and put the name of the generated files in .gitignore so they won't show up in git status Maybe like this: *.dat *.pdb — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWG4U4T7JLWWFPXBH2CPFHTU537DNANCNFSM5PWJ6E3A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[szabgab]

Then I'd probably store them in some other directory and for the purpose of the demo I'd ask the user to copy them (or do that automatically) to the directory where they are used and from where the app will delete them.

[dorigabay]

I moved the files out from this repository and added a link to download them directly from the GitHub repository of the website.
(link is under the "How to use the tool:")