Closed jikrant3 closed 1 year ago
Hi @jikrant3, thank you for your suggestions. I will try to find a way to incorporate item 1 as a feature. I think item 2 may not be required if item 1 is implemented (also, the errors will be very high if the bin has little-time/few-counts, and such data points should not be used).
Hi @jikrant3, A new function, curve_orbitwise, has been added. It can be used to create a light curve for a source, generating one data point per orbit. I am closing this issue since the feature has been realised. Please let me know if you face any bugs.
Presently, curvit requires bins of particular seconds for generating lightcurve.
1) I request a way to get counts per orbit. This is particularly useful for variables witch have larger periods or observations that were done over multiple epochs.
In the present version, if we give a 500s bin, some counts before/after the bin may be ignored due to incomplete coverage, or an orbit with ~400 s is/should be ignored. With the proposed approach, the bins will be equal to orbits, so all the events are utilized.
2) Currently, there are no errors (~ binwidth/2) in the time values. If you add the per orbit counts, you should also add the error/width of each data point in the output file.