GSoC 2019: Project IRISpy 0.2¶
Progress has been better than expected… Within the past few weeks, while continuing work on the main PR (which can be accessed via this link) on enabling a time-dependent effective areas determination in the “iris_tools” file, which contains some IRIS instrument tools, most of the previous difficulties of translating from the IDL programming language to the Python language have been identified and ironed out. In hindsight, for me the hardest part was to comprehend a computing language for which I have no direct access to (as I do not have in possession a valid IDL licence), but at the same time be able to gain enough insight through freely available online documentation to check the rough work put into place earlier in another PR. Through careful and systematic checking, I have been able to move ahead and implement the new function fit_iris_xput() as well as the get_iris_response() function in a pythonic way with some heavy dose of guidance from my mentors Dr. Dan Ryan and Dr. Laura Hayes well ahead of schedule.
For example, instead of converting from seconds to years by brute force with the conversion factor:
1yr2sec = np.float64(365.25*24.*3600.) 2t_diff = t_obs - t_cal_coeffs 3t_diff = t_diff/yr2sec
we opted to use Astropy’s powerful Units and Quantities “machinery” for the conversion instead, in the following manner:
1t_diff = t_obs - t_cal_coeffs 2t_diff = t_diff.flatten() 3t_diff = [x.to(u.year) for x in t_diff]
It has been necessary to flatten the numpy array into an 1D object to allow the list comprehension to be applied.
So the plan ahead would be to incorporate the newly implemented time-dependent fitted response into the wider IRISpy code base.
Commentscomments powered by Disqus