-
Notifications
You must be signed in to change notification settings - Fork 0
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
initial task creation #1
base: main
Are you sure you want to change the base?
Conversation
_DefaultName = "metadetect" | ||
|
||
# @pipeBase.timeMethod | ||
def run(self, calExpList: typing.List[lsst.afw.image.ExposureF], skyInfo: pipeBase.Struct) -> pipeBase.Struct: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can we split this list by band, so we can coadd each band separately?
If I do calexp.get()
I can see the filter but not before I load it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At what stages will the different bands come together? If we're coadding each band separately (and not making a measurement on a multiband coadd), we could invoke a task with only tracts and patches from a single band. Let me check what API exists to see the calexp info without loading it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, so calexp.dataId['band'] will give the abstract band like z
for the example, and calexp.dataId['physical_filter'] will output HSC-Z
.
doc=("Coadded image"), | ||
name="ngmixCoadd", | ||
storageClass="ExposureF", | ||
dimensions=("tract", "patch", "skymap", "visit", "instrument") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"visit" does not make sense for a coadd output dimension. @esheldon says he wants one output per band
so this should be band
here. I don't know if skymap
and instrument
are redundant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're probably right. I think skymap
does include instrument
but I also see some examples in the stack where both were mentioned, so I kept them both just in case.
with the new changes I get this error
|
Ugh. You need to erase the type in the database and I forget how to do this. It’s frustrating for debugging. |
So is this going to run the code once per band? That would not work for metadetect, we need all the bands. It would work if we decide to do the coadds as a separate task |
The output connections will just allow you to save one file per band. The quantum dimension in the connections constructor say whether it will be run per band. |
by "all the bands" I mean |
It cannot be done unless the associate datasets themselves are removed unfortunately. Jim's recommendation (for now) is to rename the connection output (thereby polluting the namespace) and cleaning it up once we have a basic version working. |
I tried |
How do I request only bands |
Another question: the last line currently reads
but that is only sending on coadd image, not one for each band. How is that working? |
Where you specify the dataId, include the band as well. In the example given in README, that would become |
Would you have the Struct that is returned to be modified so that it has coadded image per band? I just added one image as a placeholder and we could have several. I have to think about how to not make it specific to the |
I guess it doesn't really matter, since we are going to convert this into a |
Where can I find the output files? |
The data products will be stored in sub-folder within
If you ran it with the changed dimensions with |
do you know why |
Did you set it in your environment as given in the README example? This snippet was assuming you did that. I see on |
…tect-task into dev/arunkannawadi
DM uses non-standard naming conventions that flake8 flags
currently not seeding rng
No description provided.