Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Filenames Missing <Stdev> And <Fwhm>


dts350z

Question

  • Answers 13
  • Created
  • Last Reply

13 answers to this question

Recommended Posts

So you are saying that you have selected <stdev> and <fwhm> to be in the name of your image files, but they are missing?

 

Is your image a real, in focus, night sky image?  Maybe the software could not calculate those values for that image and just dropped them from the file name.  Are they in the EXIF data?

Link to comment
Share on other sites

Ok so I see no crash. 
If you drag one of the image that does not have the correct naming into the image preview area and click on the exif data button, looks like a rubics cube, what does the 'BackyardCaptureFwhm' and 'BackyardCaptureStdev' fields say ?

Link to comment
Share on other sites

I think you've highlighted the RA and DEC in the file name?

 

Or maybe I didn't connect the scope so the RA and DEC were blank. I'll add some separators and make sure to connect the scope tonight.

 

Thanks

 

I'm 99% sure these are FWHM and StDEV as both are exactly 5 digits, which is what these values are.  RA and DEC are different length.

Link to comment
Share on other sites

So the RA and DEC (and their separators) are missing because I didn't connect the scope?

 

Shouldn't FWHM and STDEV have decimal points in them?

 

Yes, RA and DEC are not inserted when the ASCOM telescope is not connected.

 

FWHM and STDEV are multiplied by 100, then rounded.  So 4.354 for example would be 00435 in the file name.

 

Regards,

Link to comment
Share on other sites

Decimal Points would be "problematic" for being embedded within Filenames, especially for some Image Processing Apps.

 

A Mount would need to be connected via ASCOM before BYE would have access to RA and DEC values - yes.

Similarly, you'll notice that your <fstop> parameter also didn't produce any component of the Filename - one could infer that you were Imaging with a Scope in this example.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use