[INFRA-208] Create repo for simulated spectra, etc. Created: 11/Sep/17 Updated: 16/Aug/18 Resolved: 11/Sep/17 |
|
| Status: | Open |
| Project: | Software Development Infrastructure |
| Component/s: | newitem |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | GitHub | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
We (1d simulation, 2d simulation, 1d validation) need a place to maintain the simulated spectra and their usage. Any given simulated object can be "observed" any number of times, and will need to be available for comparisons after extraction. Our strawman is a new product drp_simData We have a currently unused catID allocation (0 for sumulations, 1 for HSC). For convenience we would like to have (many) more than just one for the 1d simulations. Can we start simulation {{catId}}s at 1000 or 10000? I would like to reserve a couple for purely synthetic spectra. A second tree (data/fieldConfig/... would hold both the allocation of pfsObjects to simulated fields, and the configuration for such 2d simulations. Separate ticket. |
| Comments |
| Comment by cloomis [ 12/Sep/17 ] | ||||||||||
|
Chatted with RHL. Let's keep the {{pfsObject}}s in their own product, and put {{pfsConfig}}s in another. Assigning objects to fibers will be done by different people at different times. So we can remove one layer, and get data/$catId/pfsSimObject-$objectIdStuff.fits. And rename this product drp_simSpectra. | ||||||||||
| Comment by hassan [ 08/Jun/18 ] | ||||||||||
|
Following guideline moved issue to INFRA project. | ||||||||||
| Comment by shimono [ 19/Jul/18 ] | ||||||||||
|
@cloomis do you have any specific idea to be implemented, or say already developed a solid list of repositories?? | ||||||||||
| Comment by cloomis [ 16/Aug/18 ] | ||||||||||
|