It would appear that the Altitude Lock is not working, since a few days ago when Crescent was set to start at 18:00 and the Altitude Lock was present and there was no break between the altitude lock and the time, I loaded up SGPro again today and Crescent was still set to 18:00 when it should have shifter around 18 minutes. So is this functionality broken?
If it is not broken am I doing something wrong? Do I have to shutdown SGPro every time a sequence run has completed in order for this to update or should SGPro be left open and running? I have tried both by the way.
It just seems that it is not working for me, so I have to manually go in and ajust the times each imaging session which is a real pain when I have quite a few targets in the list.
It seems that the “Altitude is being updated” based on the time rather than the other way round
ALl the targets in that sequence are affected, so pick one, Crescent was removed from the sequence today because I did not plan on finishing the SII data
Just to clarify, when you open a target’s settings with alt lock, you are seeing the altitude change or are you seeing the altitude AND time NOT change?
Alright… I found a couple things. One was a migration issue with older sequences and another where an unrelated change broke the altitude lock. I have this mostly fixed, but still testing…
Alright… this is working again. There are many, many different permutations for a target with altitude lock. I have tested on dozens of targets (to include all the ones in your sequence) and they all seem to be happy. That said, there could be conditions that are unaccounted for. Logs now have a ridiculous amount of trace data to help with this during beta. In general, we discourage log snippets, but in this case, it’s ok.
I wouldn’t say “again”… There are so many permutations of targets on various paths at various times that, in some conditions it is broken. For this reason, I put a TON of logging in around these calculations. Could you provide that please?
Tell me what you need buddy, it did it the other day as well, I just thought it may have been something to do with the update, so I went through each of my targets and manaully updated the times which populated the altitudes, and left it open, went back to it today and it had not updated the times, so I re-loaded the sequence and it zeroed out the Altitudes
Sure… just open SGPro and then open the sequence you are using (if you dont have open last sequence on), Then click on Iris Nebula target settings. That’s it, all the junk and other calculations performed should be right in the logs.
