search

davidwhogg / SloanAtlas

code to assemble the plates of the Sloan Atlas of Galaxies
4 stars 0 forks source link

all checked in? #62

Closed davidwhogg closed 10 years ago

davidwhogg commented 10 years ago

If you do

git status

in the py and pro subdirs, is everything with a .py and a .pro file extension checked in? Also, is whatever you use to loop over quantiles making plates checked in? If these tests pass, feel free to close this issue.

ekta1224 commented 10 years ago

Most of my atlas files live in my local tractor directory so I'll need to look through them and check things into git accordingly. The quantile making code is not in so I'll put that in too.

On Feb 17, 2014, at 8:40 AM, "David W. Hogg" notifications@github.com wrote:

If you do

git status

in the py and pro subdirs, is everything with a .py and a .pro file extension checked in? Also, is whatever you use to loop over quantiles making plates checked in? If these tests pass, feel free to close this issue.

Reply to this email directly or view it on GitHubhttps://github.com/davidwhogg/SloanAtlas/issues/62 .

davidwhogg commented 10 years ago

The files that live in the tractor directory should be checked into our git repo, but in a tractor subdirectory.

There should also be some kind of README.txt that explains what directories you used on broiler and bootes and what files you ran in each place.

Sometime later this semester, we are going to try to "reproduce" your results by following the instructions in the README files...

ekta1224 commented 10 years ago

Ohh, I see. So the tractor subdirectory will contain any files in which we call tractor functions, but not the entire tractor repo, right? Since that's available for cloning on git/svn anyway. I'll start drafting the README from the various notes I have kept about my processes.

ekta1224 commented 10 years ago

is there a certain way for the README to be formatted?

davidwhogg commented 10 years ago

No, but it should be a plain text file.

ekta1224 commented 10 years ago

README.txt checked in. please let me know if it should be more detailed or include any other major processes we have carried out.

for checking in files: am i correct in assuming that any checks or tests that i wrote just to plot parameters to see our results are unnecessary to check in? they are mostly simple scripts that just use pyfits and numpy. someone familiar with fits files could easily recreate the same things for their own purposes.

davidwhogg commented 10 years ago

Yes, don't bother to check in the little scripts.

But the README should include a full set of instructions for someone who wanted to reproduce everything: tractoring, flip books, swaps, jpeg making, comment recording, and so on.

ekta1224 commented 10 years ago

closing this now because i think that all necessary files are checked in to the appropriate directories. README is in progress, opening new issue for myself on that one.