Open nickvw97 opened 8 months ago
In the code, a day is simply defined to have 60*60*24
seconds. The params.cadences_per_day
are then just an int
based on that number. If you have a hard requirement to set an exact cadence length (in seconds), then you have to modify params.cadences_per_day
so that it fits as good as possible. At the moment higher accuracy is not implemented. You would need to modify the Pandora code to do that, which should be relatively straightforward.
Dear Mr. Hippke and Mr. de Leon,
I am currently utilizing your code as part of my master's thesis, which focuses on detecting exomoons using PLATO.
During my work, I encountered an issue related to the observation cadence and the timestep in the output data. Specifically, when configuring the system for 3456 observations per day, which equates to a 25 second cadence, the resulting timestep in the data is approximately 25.1 seconds.
Although I recognize that this problem may be caused by an oversight on my part, I have not found any way to fix this problem. Following my supervisor's suggestion, I am reaching out to provide feedback through this channel. I will present the code below, where I have made the problem as clear as possible.
I appreciate your time and any guidance you can offer on this matter.
With kind regards, Nick
The result: First time point in days: 0.933785251160733 Second time point in days: 0.9340756667258174 Time step in days: 0.00029041556508446753 Time step in seconds: 25.091904823297995 Time step in seconds: 25.091904823307587