Venting about weird computer shit:
I have a Python program which does a lot of signal processing. It takes about a half hour to run for one earthquake, I need to process about 5000.
It has been dying after running minutes to hours. It generates no error message, and when it dies it kills the interpreter back to the command prompt.
I didn't know where it was dying (or even if it was in the same place) so I added a print statement at the start of each function, just something like print('Starting GetPhaseInfo()') Since I added the print statements it has run for days without problem.
WTF??? I don't know whether to be happy that adding print statements fixed the problem, or frustrated that I don't even know what caused the problem. Both, I guess.
I'm mostly just venting, but if any of you have ideas I'm happy to hear them.
[#]python #coding #science
=> More informations about this toot | View the thread | More toots from wanderinghermit@mindly.social
=> View python tag | View coding tag | View science tag This content has been proxied by September (ba2dc).Proxy Information
text/gemini