Fix some of the slow down in tesscube
, fix tuple problem.
#10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mrtommyb has pointed out that
tesscube
is slower than its previous versions. I haveTESSCube
object, rather than during the TPF creation, as this is a one time calculation and can take ~1 secondPOS_CORR1
andPOS_CORR2
optional. This step requires iterating through all the SPOC assigned WCS and calculating the source position. This is costly, but I've included it as this produces the most SPOC-like TPF product. It now has an optional flag.