Author Topic: Invalid Subframe Selector Keyword  (Read 2402 times)

Offline SeattleStarGazer

  • Member
  • *
  • Posts: 50
Invalid Subframe Selector Keyword
« on: 2017 July 20 14:10:59 »
Using SFS for the first time. Entered a weighting expression that I got from a spreadsheet that worked and I entered SFSWEIGHT for the keyword and output the frames. I then registered the frames and tried image integration and got this error message

Error: D:/Astro/Pelican/Registered/Pelican--%2017-07-14--1x1--frame2_c_cc_a_r.xisf: Nonexistent or invalid weight keyword 'SFSWEIGHT'.
<* failed *>

This was the expression

18*((1/(FWHM^2))-0.124861092035111)/0.158072362016496 + 6*(1-(Eccentricity-0.374)/0.411) + 36*(SNRWeight-0.755)/0.081 + 40

I did check the FITS headers and the keyword was there and spelled correctly. Any ideas?

Offline RickS

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1298
Re: Invalid Subframe Selector Keyword
« Reply #1 on: 2017 July 20 18:29:55 »
The only times I have had an error like this it has been user error (I ran registration on files in the wrong directory, had an old file lying around, etc.)

Cheers,
Rick.

Offline mschuster

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1087
Re: Invalid Subframe Selector Keyword
« Reply #2 on: 2017 July 20 20:16:12 »
Double check that all weights are positive. Zero and negative weights will cause this error.

Also you might want to use a keyword with at most 8 letters. I think this is an official FITS requirement. PI may be able support more, so this might not be the problem.

Offline RickS

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1298
Re: Invalid Subframe Selector Keyword
« Reply #3 on: 2017 July 20 20:35:50 »
Double check that all weights are positive. Zero and negative weights will cause this error.

Also you might want to use a keyword with at most 8 letters. I think this is an official FITS requirement. PI may be able support more, so this might not be the problem.

I have used the keyword "SFSWEIGHT" successfully, Mike, but checking for a zero or negative value is a good suggestion.