Regarding BOOST.Astronomy
Hello everyone, I am not able to understand what exactly is to be done to complete the parser for FITS and I have also tried understanding the codebase but I am not getting what is the work done till now. Can you also provide some resources? Thanking you Sarthak Singhal
I would suggest you to first understand what's FITS file and it's structure [1]. Once you know it, codebase will became extremely easy to understand. Currently parser can parse primary HDU and image extensions. Parser for binary table extension and ASCII table extension is to be implemented. [1]: https://archive.stsci.edu/fits/fits_standard/node1.html On Thu 28 Mar, 2019, 1:28 PM Sarthak Singhal via Boost, < boost@lists.boost.org> wrote:
Hello everyone, I am not able to understand what exactly is to be done to complete the parser for FITS and I have also tried understanding the codebase but I am not getting what is the work done till now. Can you also provide some resources? Thanking you Sarthak Singhal
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Am I considering it right that similar to image.hpp I have to create one file for binary table and one for ascii table to store the data? In this I have to use the fact that in ascii table the data values will be ascii characters and in binary table the data value will be a byte(i.e. 8 bits) and both will have their data array as two-dimensional. For the astronomical coordinate conversion part I am considering Horizontal-Equatorial,Ecliptical-Equatorial, Equatorial-Galactic conversions using different transforms. Is there something more that need to be done and am I considering it in the right way? Thank You Sarthak Singhal -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html
On Fri, Mar 29, 2019 at 2:01 AM sarthak2007 via Boost <boost@lists.boost.org> wrote:
Am I considering it right that similar to image.hpp I have to create one file for binary table and one for ascii table to store the data?
It depends on how you chose to implement the scheme to store the data.
In this I have to use the fact that in ascii table the data values will be ascii characters and in binary table the data value will be a byte(i.e. 8 bits) and both will have their data array as two-dimensional.
Binary data does not always need to be of 8 bits For the astronomical coordinate conversion part I am considering
Horizontal-Equatorial,Ecliptical-Equatorial, Equatorial-Galactic conversions using different transforms. Is there something more that need to be done and am I considering it in the right way?
You are considering it right but there are lot more classes(whole hierarchy of coordinate systems) that need an update for Boost.Units. -- Thank you, Ruchika Joshi
participants (4)
-
Pranam Lashkari -
Ruchika Joshi -
Sarthak Singhal -
sarthak2007