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

File output: simple change #19

Closed
rmandelb opened this issue Jul 18, 2014 · 5 comments
Closed

File output: simple change #19

rmandelb opened this issue Jul 18, 2014 · 5 comments

Comments

@rmandelb
Copy link
Collaborator

Hironao would like to change the file output so that the filename automatically includes visit/CCD or tract/patch or some other unique-ish identifier, so that plots don't get overwritten when you make a new one for a new CCD. I believe he said this should be a simple change that he can do. Is that right, @HironaoMiyatake ?

@HironaoMiyatake
Copy link
Collaborator

Yes, I think so at least for the CCD level. I'll make a change based on branch #7.

@HironaoMiyatake
Copy link
Collaborator

I added a simple change for this.
For CCD-level tests, a filename is
$SUPRIME_DATA_DIR/rerun/[rerun/name/for/stile]/%(pointing)05d/%(filter)s/stile_output/[sys_test_name]-%(visit)07d-%(ccd)03d.png
. For field-level tests, a filename is
$SUPRIME_DATA_DIR/rerun/[rerun/name/for/stile]/%(pointing)05d/%(filter)s/stile_output/[sys_test_name]-%(visit)07d-[ccds].png
, where [ccds] is a reduced form of a CCD list. For example, if a CCD list is [0, 1, 2, 4, 5, 6, 8, 10], [ccds] becomes 0..2^4..6^8^10.

Do we want to merge this change to the PR of #7 , or do we want make a PR for this branch after merging #7 to master?

@msimet
Copy link
Owner

msimet commented Jul 22, 2014

If you don't mind merging it into #7, let's do that--this is much better!

@HironaoMiyatake
Copy link
Collaborator

Done! Shall we close this issue?

@msimet
Copy link
Owner

msimet commented Jul 23, 2014

Sure! Closing...

@msimet msimet closed this as completed Jul 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants