You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a function that takes in a 94, 171, and 193 image and returns a "hot" 94 image. These should be level 1.5 images, with equivalent dimensions.
Potentially, this could go in some new subpackage (maybe analysis?) as it does not really fit into any of the current ones. There should probably also be some discussion about whether this is in the scope of this package at all...
A quick mockup of what this could look like
deffilter_94_hot(m_94, m_171, m_193):
# Check that all are 1.5, of equivalent dimensions, error if they aren'tc_fit= [-7.19e-2, 9.75e-1, 9.79e-2, -2.81e-3]
A_fit=0.39B_fit=116.32f_fit=0.31I_max_fit=27.5I_94_warm=0.0fori,cfinenumerate(c_fit):
ifi>0:
x= (f_fit*m_171.data+ (1-f_fit) *m_193.data) /B_fitx[x>=I_max_fit] =I_max_fitelse:
x=1I_94_warm+=A_fit*cf*x**i# Make metadata modifications to indicate this has been filtered?returnm_94._new_instance(m_94.data-I_94_warm, copy.deepcopy(m_94.meta))
The text was updated successfully, but these errors were encountered:
I hadn't actually thought of that. Currently, we don't add/change any metadata when doing the degradation correction so I'm not sure of an easy way to check for this.
I would probably just leave this up the user to figure out beforehand whether they need to do this.
In GitLab by @wtbarnes on May 14, 2021, 08:26
There are several established methods for filtering 94 images to isolate the "hot" component which is dominated by Fe XVIII, e.g. https://iopscience.iop.org/article/10.1088/0004-637X/759/2/141.
It would be nice to have a function that takes in a 94, 171, and 193 image and returns a "hot" 94 image. These should be level 1.5 images, with equivalent dimensions.
Potentially, this could go in some new subpackage (maybe
analysis
?) as it does not really fit into any of the current ones. There should probably also be some discussion about whether this is in the scope of this package at all...A quick mockup of what this could look like
The text was updated successfully, but these errors were encountered: