-
Notifications
You must be signed in to change notification settings - Fork 7
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
DM-37951: Allow PTC analysis to split each amp into subregions #171
base: main
Are you sure you want to change the base?
Conversation
|
||
# interpolate + smooth | ||
itp = interp1d(x,y, kind='linear') | ||
window_size, poly_order = 101, 3 |
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.
These should probably be config options. Was 101 chosen for a particular reason, or is just "an odd integer about 100"?
# Now split the region into subregions | ||
xStep = int(region.width / nSubX) | ||
yStep = int(region.height / nSubY) | ||
for iSub in range(nSubX): |
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.
It's probably not worth the effort now, but this could have used the cpCombine.CpCombineTask._subBBoxIter
static method to chunk the image and reuse code.
for ampName in ampNames: | ||
datasetPtc.inputExpIdPairs[ampName].append(partialPtcDataset.inputExpIdPairs[ampName]) |
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.
Doesn't this change the dimensionality? Previously the partial inputs were lists of tuples, appended into a list-of-list-of-tuples. Using +=
flattens it into a list-of-tuples again. I think this less of a problem below, as it looks like it was just selecting the first element of the input lists for those entries.
This is working, but I'm sure has things that need correcting. Summary of the status is in the Jira ticket.