FPP is NaN and NFPP is 0.0 about triceratops HOT 8 CLOSED

Hi, the solution is, as Steven already said, in the binning of the folded lightcurve. But 250 seems to be too much.
After also struggling with NaN values, since I use bins=100, no more problems. And I use Triceratops a lot...
I'm afraid I can't explain why this works, but it does...
I tried your file with bins = 100 and got:

from triceratops.

Interesting. Thanks for your answer. The only thing that concerns me is the fact that using only 100 points to represent the transit with some baseline could be not enough to properly compare it to any given model. What do you think?

from triceratops.

I'm not an expert, but quoting Steven in example.ipynb of this repository:
"If you have a lot of data points, I recommend binning your light curve down to ~100 to save time. Binning your data is poor practice when fitting light curves for a planet's parameters, but it doesn't yield significantly different results for our purposes"

from triceratops.

Don't know why I read 1000 instead of 100. Thanks for pointing it out.

from triceratops.

That still doesn't explain why we can't use more points, but I'll stick to that number of bins given it makes the algorithm work properly most of the times.

from triceratops.

I have been having similar problems, though it might not be related. In my case, the code only sometimes returns NaNs (I assume because whatever is producing NaN is part of the random draw process). Some combinations of lightcurves and contrast curves seem more likely to produce NaNs. In particular, I seem to be getting the most NaNs when I use the more constraining contrast curve; 8 of the FPPs out of the loop of 20 I just ran are NaN.

from triceratops.

I've run into that issue with contrast curves too and have come up with a solution, but I haven't pushed it to the repo yet. I'm hoping to update the code with a fix for both of these within the next ~2 weeks.

from triceratops.

Okay, these issues should be resolved with the latest update (1.0.9), which I just pushed. You should now be able to run the code with all of your data points (I'm sure there is an upper limit, but I have't encountered it) and any contrast curve. I'm going to close this thread, but definitely open it again if you continue to run into these issues.

from triceratops.