Should Feature Tracking work while running python scripts or the sequencer? I tried with Python but it stopped after a little bit.
Alternatively, it'd be nice to be able to access the calibration data and routines for doing Center of Mass calculations from within those tools.
Feature Tracking & Scripting/Sequencing
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
-
admin
- Site Admin
- Posts: 13362
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Feature Tracking & Scripting/Sequencing
Hi,
right now there is no access to the feature tracking information from sequencer or scripting, so it has to be launched and managed through the menus and its own user interface.
I can't see any reason why feature tracking would have to stop or would fail when using scripting, but it might depend on what the script does - perhaps certain actions or changes might disable feature tracking or stop it from tracking properly.
What are you trying to do with scripting while feature tracking is active?
cheers,
Robin
right now there is no access to the feature tracking information from sequencer or scripting, so it has to be launched and managed through the menus and its own user interface.
I can't see any reason why feature tracking would have to stop or would fail when using scripting, but it might depend on what the script does - perhaps certain actions or changes might disable feature tracking or stop it from tracking properly.
What are you trying to do with scripting while feature tracking is active?
cheers,
Robin
Re: Feature Tracking & Scripting/Sequencing
We're trying to capture SER files and launch programs to do additional processing (specifically PlanetarySystemStacker and sftp).
The script does set a bunch of camera control values:
scc.Binning.Value = '1'
scc.ColourSpace.Value = 'MONO16'
scc.BlackLevel.Value = 100
scc.OutputFormat.Automatic = False
scc.Gain.Value = 0
scc.Resolution.Value = '1000x1000'
scc.OutputFormat.Value = 'SER file (*.ser)'
The script does set a bunch of camera control values:
scc.Binning.Value = '1'
scc.ColourSpace.Value = 'MONO16'
scc.BlackLevel.Value = 100
scc.OutputFormat.Automatic = False
scc.Gain.Value = 0
scc.Resolution.Value = '1000x1000'
scc.OutputFormat.Value = 'SER file (*.ser)'
-
admin
- Site Admin
- Posts: 13362
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Feature Tracking & Scripting/Sequencing
Hi,
things that change the size or bit depth of the image will stop and restart the camera, and that could have an impact on the feature tracking. In your scripting example, setting the binning, resolution or colour space *could* do that (if the values you are setting are different to the existing ones). If the values are already set to the same ones that the scritp tries to set then it should be smart enough to ignore the 'changes'.
cheers,
Robin
things that change the size or bit depth of the image will stop and restart the camera, and that could have an impact on the feature tracking. In your scripting example, setting the binning, resolution or colour space *could* do that (if the values you are setting are different to the existing ones). If the values are already set to the same ones that the scritp tries to set then it should be smart enough to ignore the 'changes'.
cheers,
Robin