Open vikdhillon opened 4 years ago
trmrsh
commented
4 years ago Ah, I was struggling to work out what I had done to trm-drivers and then realised that I had started a mass of python2 to 3 changes, but not finished them. There are sure to be a huge stack of bugs, so I am not going to be change this anytime soon. I had better start experimenting with a new version on the rack when I can; going to be difficult.
trmrsh
commented
4 years ago Ah, sorry being stupid. I switched back to the old master branch (been off it for an age) and I think I should have fixed the drift mode rtplot issue. It will need Paul to update usdriver on the rack. Suggest doing so tomorrow morning in good time, but it should be easy to roll back if need be. If t works, please say so here and close the issue.
vikdhillon
commented
4 years ago Hi Tom,
Paul and I have been looking at re-installing usdriver.py
We've noticed that you must have been installing this in the past, as it is in /home/observer/trm on the rack PC (and a call to your version is hardcoded in start_uspec).
Paul has only ever installed the old java version.
Do you want to install it, or would you like Paul to? If the latter, then he'll probably need some instructions? I'm copying Paul into this.
Cheers,
Vik.
On Mon, 24 Feb 2020 at 22:31, Tom notifications@github.com wrote:
Ah, sorry being stupid. I switched back to the old master branch (been off it for an age) and I think I should have fixed the drift mode rtplot issue. It will need Paul to update usdriver on the rack. Suggest doing so tomorrow morning in good time, but it should be easy to roll back if need be. If t works, please say so here and close the issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/trmrsh/trm-drivers/issues/3?email_source=notifications&email_token=AC46DHEZNA2JSGLBJRXKCADRERDDTA5CNFSM4K2LODBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZZGNQ#issuecomment-590582582, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC46DHD4RTOM4YH7XSTNV5TRERDDTANCNFSM4K2LODBA .
trmrsh
commented
4 years ago Let me have a look. I seem to recall the rack PC may not have git, but hang on.
trmrsh
commented
4 years ago I encountered a problem; can Paul comment on it? May be this is the problem with git I remember.
git pull fatal: unable to access 'https://github.com/trmrsh/trm-drivers.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
trmrsh
commented
4 years ago OK, I am starting to remember. It works on the drpc and I need to copy it over. This is probably not a good time for this is it?
vikdhillon
commented
4 years ago Would it be easy to revert to the old version? It would be useful to have setup windows working as we've got another 2 drift mode runs, but not if you think this would be a risky change. Cheers, Vik.
On Tue, 25 Feb 2020 at 10:45, Tom notifications@github.com wrote:
OK, I am starting to remember. It works on the drpc and I need to copy it over. This is probably not a good time for this is it?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Plotting the setup windows in rtplot (setwin=true) is a really useful feature when acquiring in drift mode. Unfortunately, it does not work with ULTRASPEC, with rtplot in the hipercam pipeline reporting that "No valid data are available", even when trying to plot setup windows which are identical in size to the drift mode windows (so they definitely are valid window parameters). Note that a similar error is reported when the ultracam pipeline is used instead. The url being used is http://192.168.1.2:5100. Note that everything works fine in non drift mode, so the problem is definitely in usdriver.