fix(Updated-Effelsberg-Clock-Files): added clock file for Effelsberg …

[tabbott36]

No description provided.

[dlakaplan]

Thanks for this. Will these files ever change/need updating? If so, how should that happen? Also, I think we may need a new entry in:
https://github.com/ipta/pulsar-clock-corrections/blob/main/pulsar_clock_corrections.py#L1315
If there is any procedure there for documenting the updates or who to contact, that would be the place to include it.

[tabbott36]

My pleasure!

The files corresponding to the old Effelsberg backends (Effelsberg and Effelsberg Asterix/PSRix) should not need to be changed as they are no longer used for PTA observations. However, the EDD file added in this PR will need to be updated regularly. I've recently taken over Effelsberg PTA observations, so will be updating the clock files regularly. Is there a particular way and cadence you'd like me to do this?

Thanks for the link, I'll have a look at https://github.com/ipta/pulsar-clock-corrections/blob/main/pulsar_clock_corrections.py#L1315 and update the Effelsberg documentation/contact info.

[dlakaplan]

My pleasure!

The files corresponding to the old Effelsberg backends (Effelsberg and Effelsberg Asterix/PSRix) should not need to be changed as they are no longer used for PTA observations.

Good to know. Are they in use for any other observations (other timing programs)? It might be still useful to include them if possible.

However, the EDD file added in this PR will need to be updated regularly. I've recently taken over Effelsberg PTA observations, so will be updating the clock files regularly. Is there a particular way and cadence you'd like me to do this?

On what cadence do you update the files locally? We can easily automate a download of the file if you host it somewhere. Otherwise, we would do manual updates on whatever cadence is most useful/least disruptive.

Thanks for the link, I'll have a look at https://github.com/ipta/pulsar-clock-corrections/blob/main/pulsar_clock_corrections.py#L1315 and update the Effelsberg documentation/contact info.

[tabbott36]

Good to know. Are they in use for any other observations (other timing programs)? It might be still useful to include them if possible.

Not that I'm aware of. That's a good point though, I'll aim to include them when generating the updated clock files. Thanks!

On what cadence do you update the files locally? We can easily automate a download of the file if you host it somewhere. Otherwise, we would do manual updates on whatever cadence is most useful/least disruptive.

We don't have a set schedule at the moment, though I hope to do it every few months just to be sure the scripts we use to generate the clock files are still working smoothly. For now, I think manual updates are not inconvenient, happy to go with that!

[dlakaplan]

OK, sounds good. When you have the new info block created we can check if the whole system will build properly. Hopefully it will be easy from there.

[dlakaplan]

A related question is how/when do you update these files for tempo(2)? We can also pull the files from there if that's easier.

[tabbott36]

I also upload these files to the EPTA clock files repo and I believe they update them for tempo2. I'm not sure who is in charge of that. I'll ask around to see. Indeed, it would be more elegant to have that be done automatically.

[dlakaplan]

I see:
https://bitbucket.org/psrsoft/tempo2/src/master/T2runtime/clock/effedd2gps.clk

which looks to be the same file, but somewhat old. It would be good to understand how the updates go from Effelsberg -> this repo/tempo2.

[dlakaplan]

You are also replacing the Effelsberg Asterix file. That's another one that we normally pull from tempo2. Should we continue to do that? Note that those updates have failed recently because the file changed too much. But we can override that if that's useful, and it looks like the file you are trying to upload is the same as the tempo2 one, so that might be a simpler plan.

[dlakaplan]

@jorisverbiest: I think you can join this thread if you want