search

GRIFFINCollaboration / detectorSimulations

GEANT4 simulation code for the GRIFFIN array and it's suite of ancillary detection systems.
7 stars 13 forks source link

LaBr3 changes in orientation #56

Closed christinaburbadge closed 10 years ago

bkatiemills commented 10 years ago

This looks great @christinaburbadge ! It looks like it inherits a lot from the old Brillance code; is this intended to replace that code, or be an alternative to it? If this replaces it, can you please remove the old stuff (both the files and the commented-out functions in your files files) from the code? Let me know!

christinaburbadge commented 10 years ago

Hi Bill,

I did intend for the Lanthanum Bromide code to replace the BrilLance code, but Evan would like to delete it himself as he would like to back it up first. I did however remove the commented-out functions, and have a pull request for the final copy.

Thanks,

Christina

----- Original Message ----- From: "Bill Mills" notifications@github.com To: "GRIFFINCollaboration/detectorSimulations" detectorSimulations@noreply.github.com Cc: "christinaburbadge" cburbadg@uoguelph.ca Sent: Saturday, 8 February, 2014 5:59:04 PM Subject: Re: [detectorSimulations] LaBr3 changes in orientation (#56)

This looks great @christinaburbadge ! It looks like it inherits a lot from the old Brillance code; is this intended to replace that code, or be an alternative to it? If this replaces it, can you please remove the old stuff (both the files and the commented-out functions in your files files) from the code? Let me know!

— Reply to this email directly or view it on GitHub .

bkatiemills commented 10 years ago

Sounds good @christinaburbadge - thanks for letting me know! But, @evan012345 - you understand that github has every single commit backed up for you, right? If you're ever feeling nostalgic for the past (or you mess up big time and need to go back), just do a 

git reset --hard <commit hash>

where <commit hash> is the string of seemingly garbage characters that goes along with every commit (you can see them by doing a git log at the command line) - no need to back stuff up by hand. Do be careful with reset though - it will completely reset your version on your computer to whatever commit you asked for, so do not do it until you first commit whatever you've been working on, or you will blow away work!

If you just want to peek at an older version without changing anything on your computer, you can use the web interface to go snooping, too.

evan012345 commented 10 years ago

Thanks Bill, I am aware that GitHub backs up all of our commitments/versions. I'm still old school with my local backups. You never know... GitHub's multiple RAID servers could all simultaneously spontaneously combust. Happens every day...

On Wed, Feb 12, 2014 at 1:21 PM, Bill Mills notifications@github.comwrote:

Sounds good @christinaburbadge https://github.com/christinaburbadge - thanks for letting me know! But, @evan012345https://github.com/evan012345- you understand that github has every single commit backed up for you, right? If you're ever feeling nostalgic for the past (or you mess up big time and need to go back), just do a

git reset --hard

where is the string of seemingly garbage characters that goes along with every commit (you can see them by doing a git log at the command line) - no need to back stuff up by hand. Do be careful with resetthough - it will completely reset your version on your computer to whatever commit you asked for, so do not do it until you first commit whatever you've been working on, or you will blow away work!

If you just want to peek at an older version without changing anything on your computer, you can use the web interface to go snooping, too.

Reply to this email directly or view it on GitHubhttps://github.com/GRIFFINCollaboration/detectorSimulations/pull/56#issuecomment-34898664 .