-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Y2000.phs file #53
Comments
@dylanmikesell thank you so much for the bug report. I'll fix it. |
Did this get fixed? I do not see a commit related to this issue, but maybe it just was not tagged. |
Hi Mikesell,
Not yet, but I will work on it.
Regards,
Mostafa
…On Mon, Apr 18, 2022, 10:08 AM Dylan Mikesell ***@***.***> wrote:
Did this get fixed? I do not see a commit related to this issue, but maybe
it just was not tagged.
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADHWAPDBFXUPWBMFLF6ZBEDVFWJI7ANCNFSM4ZHMWYRA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Dear Mustafa, I am also interrested in this part of the code. |
Hello, I haven’t done the fix as this was just a rough association and
since then several association codes came out. I recommend to use Gamma or
Octoapy instead.
Mostafa
…On Thu, Jan 25, 2024, 5:13 AM juracimario ***@***.***> wrote:
Dear Mustafa, I am also interrested in this part of the code.
Cheers,
Juraci
***@***.***)
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADHWAPB37JWB5T56FAJG6JDYQJLA3AVCNFSM4ZHMWYRKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJRGAYTSOBQG44Q>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I think there is a small bug in the line that writes the event information (lines 411-414 in associator.py).
In the case where minutes is less than 10, the columns are not correct in the resulting phase file. Compare the two events below. The first event has a start time of 2021-10-01 01:33:06.05, but the 0 in front of the six is missing and thus this line has one less column than the next event, start time of 2021-10-01 01:34:43.42. This completely screws up an parser that reads by position.
It would be nice to modify the code to put zeros in front of the single digit numbers that should be two characters long.
I guess it is most important for the seconds (%04.2f).
The text was updated successfully, but these errors were encountered: