foxsi / foxsi-science

Analysis tools to reduce and analyze data from the FOXSI sounding rocket flights
7 stars 13 forks source link

Update the effective areas for the different flights. #64

Open pymilo opened 5 years ago

pymilo commented 5 years ago

For the third flight, we had two new 10-shell modules and two 7-shell with honeycomb collimators attached of the front. These four modules have different from FOXSI-2 EAs.

somusset commented 5 years ago

Do we have measurements for these new effective areas? Is this something you are working on? Do you need inputs from someone?

pymilo commented 5 years ago

We have the measurements for the two new 10-shell modules: X7 - https://drive.google.com/open?id=1aG3hQnnLgeiY1rTK2Qw9VBtCGDkrtjIo X8 - https://drive.google.com/open?id=1YPG_ag5TTtUKuUK46kjmk9-N5nh1Qp_k

For these two, we need to extract the data and put it the format of the FOXSI-Soft.

For the 3D-printed collimator, the only data we have (US-side) is the geometric cross-section measured with the CCD camera. We can ask our Japanese colleagues whether they have measurements of the effective area for their module with the collimator attached (I think they have).

For our side, we can work out an estimate of the effective area based on the open area of the collimator, the effective area of the 7-shell module and the vignetting effect as a function of the off-axis angle.

LinErinG commented 4 years ago

At the 1/22/2020 meeting it was decided that we need some small code updates to foxsi_get_optics_effarea.pro to incorporate Milo's new information. Milo is going to work on that.

pymilo commented 4 years ago

The foxsi_get_optics_effarea.pro was already optimized to get the dimensions out of the calibration files themselves. It should already work for FOXSI1 and FOXSI2 analysis. @somusset please have a look at the changes I implemented. In theory, the foxsi_get_optics_effarea.pro should not affect any of the code you have for analyzing foxsi 1 and 2 data. Can you please do a sanity check for em> :)