add a gAperture flag for AIS legs 1-3

[cmillion]

CAI mode only?

[cmillion]

The flag number is 256. I've also updated the User Guide.

[cmillion]

As implemented, this adds substantial overhead to FUV light curve. In the time it took to generate ~4,000 NUV light curves, only ~260 were created in FUV. I'm trying to refactor it to be a little more reasonable.

[cmillion]

I'm deprecating this feature for now, until I have a burst of clever. I don't know how to handle common edge cases without making FUV unusably slow.

[cmillion]

I'm thinking now that the fastest and most robust way to do this might be to pre-build a table of time ranges delimiting the case where you have FUV CAI legs 1-3, and then download that whole table once at the beginning of each run and quickly check for overlaps.

[bshiao]

Yep, that makes sense, I’ll think about it

From: Chase Million [mailto:[email protected]]
Sent: Friday, June 24, 2016 10:54 PM
To: cmillion/gPhoton
Subject: Re: [cmillion/gPhoton] add a gAperture flag for AIS legs 1-3 (#207)

I'm thinking now that the fastest and most robust way to do this might be to pre-build a table of time ranges delimiting the case where you have FUV CAI legs 1-3, and then download that whole table once at the beginning of each run and quickly check for overlaps.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/207#issuecomment-228504493, or mute the threadhttps://github.com/notifications/unsubscribe/AGjjw_THERDl-Y1OyF5P-6v4P2eHNOkxks5qPJhcgaJpZM4IY1WS.

[cmillion]

Bumping this change to a later build version after we have a chance to build the above-discussed lookup table.