Beta nearly over (but some new features snuck in too)

[admin]

Can a python script be run from within the sequencer? Perhaps having a script that just does the flip and reacquires the target that could be run from the sequencer would be the simplest way to go.

Yes, you can run a script from the sequencer (or run a sequence from the scripting, but I wouldn't advise trying to go recursive on that!).

cheers,

Robin

[admin]

Can a python script be run from within the sequencer? Perhaps having a script that just does the flip and reacquires the target that could be run from the sequencer would be the simplest way to go.

Yes, you can run a script from the sequencer (or run a sequence from the scripting, but I wouldn't advise trying to go recursive on that!).

cheers,

Robin

[Borodog]

How would I do an offset goto from either the sequencer or python?

[Borodog]

Second question. How do I start and stop feature tracking from Python and change feature tracking parameters such as the correction scaling factor?

[admin]

Hi,

to turn on the offset sync/regoto, use this line from scripting

Code: Select all

SharpCap.Reticules.SelectReticule("Alignment Mark")

That displays the alignment mark on top of the image, which also enables the offset when performing the sync. Anything that primarily displays info over the image (usually without any other UI) is a 'reticule' as far as the internals of the application go. Turn it off again by setting the selected reticule to None (or trying to select an empty string - "")

Feature tracking is available via SharpCap.FeatureTracking - from that you can 'Show' the window, start the various stages (monitoring, calibration, tracking, etc) and monitor the current status via 'IsGuiding' etc. You can load a saved calibration, but there is no access to adjusting the settings from that API - the assumption is that this is to turn on/off the feature tracking under automation once it has already been configured manually. Essentially I wrote the minimum that seemed to make sense as a usable API and then left it waiting to see if anyone asked for more... So, which parameters do you absolutely need to change, or are those just a nice to have for future ideas?

cheers,

Robin

[SanjeevJ]

This is awesome, TY! I know the CLAHE settings will need to be tuned based on image scale and SNR.. but I asked my favorite AI engine to recommend some initial levels as starting points for something like RASA 8 + ZWO 2600. This is what I got as starting points.. if more specific recommendations, please share your experiences.

[Borodog]

Hi,

to turn on the offset sync/regoto, use this line from scripting

Code: Select all

SharpCap.Reticules.SelectReticule("Alignment Mark")

That displays the alignment mark on top of the image, which also enables the offset when performing the sync. Anything that primarily displays info over the image (usually without any other UI) is a 'reticule' as far as the internals of the application go. Turn it off again by setting the selected reticule to None (or trying to select an empty string - "")

Feature tracking is available via SharpCap.FeatureTracking - from that you can 'Show' the window, start the various stages (monitoring, calibration, tracking, etc) and monitor the current status via 'IsGuiding' etc. You can load a saved calibration, but there is no access to adjusting the settings from that API - the assumption is that this is to turn on/off the feature tracking under automation once it has already been configured manually. Essentially I wrote the minimum that seemed to make sense as a usable API and then left it waiting to see if anyone asked for more... So, which parameters do you absolutely need to change, or are those just a nice to have for future ideas?

cheers,

Robin

Robin,

The parameter that I need to change is the corrections scaling, and here is why. To get Feature Tracking to engage the Declination axis and quickly move the target to the center of the chip, the correction scaling needs to be large, e.g. 100%. But once the target is centered in the much smaller capture ROI, the correction scaling needs to be small, e.g. 20% at most, else the target lurches back and forth with every correction applied.