Fix Version/s: None
Sprint:AP F19-6 (November)
While doing the gen3 DECam work, I started a document describing how to write a gen3 obs package. That document will be fleshed out as part of doing the obs_lsst gen3 cleanup, and this ticket is to finally publish it. It will live in obs_base/docs/lsst.obs.base/.
- is duplicated by
DM-4624 Documentation on how to create a new obs package
- is triggered by
DM-20763 Add initial support for Gen3 Butler to obs_decam
DM-16297 Add Gen3 Instrument and Formatter classes for obs_lsst
Tim Jenness: is the gen3 obs system stable enough that this could finally be completed? I suspect that I am no longer in a good place to write it now, given changes since I last worked on the obs packages. I've seen the queries from various people wanting to write gen3 obs or update their gen2 obs package: might be nice to take care of all of those questions at once with these docs.
For what it's worth, I've just finished making obs_necam gen3 compliant....
James Mullaney excellent. Note that you don't need to call it lsst.obs...
Let me know if you want some feedback.
John Parejko, yes, it's on the list. I'll assign it to me.
@tjenness Yes, feedback would be great, thanks. Perhaps best to put them as Issues in the GitHub repository. Be kind
Not sure what you meant by "you don't need to call it lsst.obs...", though. Do you mean in the bin/run_gen3_demo.sh file?
I mean in your obs_necam package itself. Gen3 doesn't require all obs packages use lsst.obs. in the module name. Obviously you can do that but you don't need to.
Oh, I see what you mean. Thanks for explaining that.
John Parejko I updated your text a little to keep it up to date but decided to merge now so that it's in the next weekly. I reassigned it to you since you did the work and I reviewed.
This is on hold while we sort out remaining design issues.