rodluger / everest Goto Github PK

@rodluger Will campaign 14 EVEREST 2.09 light curves be available soon? (Asking for a collaborator). -Eric

If I didn't made any mistake in my interpretation of the code, there seems to be a puzzling difference between what the code does and what the Luger+2017 paper says that the code is doing regarding the cross validation of rPLD. In the paper, it's mentioned that "we split each light curve segment into three roughly equal sections. For each pair of sections, we train the model on them and compute the model prediction in the third section (the validation set)".
From the code below, it looks like the training set is actually the whole chunk and the validation set is a pair of sections within the chunk.

Did I misunderstood the code ?
If no, this way of selecting validation and training sets is strange because it implies that the validation set is actually 2/3 of training set. The validation set should in principle be independent from the training set, right ? Is there a reason to do this anyway ?

I'm playing around with some short cadence targets and I noticed that my code stalls because it seems to want to download the short cadence TPF even if cadence='lc'. I think that it would be possible to change this line to avoid this? Thoughts?

i am a graduate student,i am very interested in your code,but i can not run your test example.Is the test_detrend is an example for the detrending,i am not sure whether i run right or wrong.could you help me or give me another specific example,thank you very much @rodluger

I am trying to run everest.standalone.DetrendFITS on short cadence data in a Jupyter notebook. When the procedure gets to the "computing the model" step, eventually I get a message that the Kernel has hung and has to reststart. I am running Python 2.7.3 on a macbook pro (OS 10.13.2 2.2 Ghz Intel core i7, 16GBYT memory)

It runs fine with long cadence data.

Update-I tried running it from the command line and received an error that I was out of application memory. I stopped all other applications but still got the error. Has anyone else tried running it on sc data and has a tip or trick?

Installed everest-pipeline 2.0.11 on Windows 10 with the latest python, but cannot get past "import everest" in an app with these errors:

...\Python\Python37-32\lib\site-packages\everest_init_.py", line 22, in
from . import mathutils
...\Python\Python37-32\lib\site-packages\everest\mathutils.py", line 16, in
from scipy.misc import comb
ImportError: cannot import name 'comb' from 'scipy.misc' (...\Python\Python37-32\lib\site-packages\scipy\misc_init_.py)

this fix: from scipy.special import comb
...

When past the above (after fix mentioned) I get this:

File "...Python\Python37-32\lib\site-packages\everest_init_.py", line 23, in
from . import transit
File "...Python\Python37-32\lib\site-packages\everest\transit.py", line 19, in
import pysyzygy as ps
File "...Python\Python37-32\lib\site-packages\pysyzygy_init_.py", line 16, in
subprocess.call(["make"], cwd = cwd)
File "...Python\Python37-32\lib\subprocess.py", line 323, in call
with Popen(*popenargs, **kwargs) as p:
File "...Python\Python37-32\lib\subprocess.py", line 775, in init
restore_signals, start_new_session)
File "...Python\Python37-32\lib\subprocess.py", line 1178, in _execute_child
startupinfo)
FileNotFoundError: [WinError 2] The system cannot find the file specified

Any ideas? And pysyzygy installed just fine.

Dear Rodrigo,

A minor issue in the /everest/missions/k2/ source, but I believe "aux" is a reserve word in Windows back to the MS DOS days where a file cannot be so named. Would it be possible to rename this to something else, so Windows users don't have to manually fix this in the setup code for each new EVEREST update?

Thanks, Mark

It's now pretty much impossible to install george 0.21 (there may be a way to git checkout an older version, but it's a hassle!). Any chance of updating everest to run with 0.3? There's not too much difference, except that WhiteKernel is now part of the george.GP object rather than existing as a stand-alone kernel. Hence the import error:

ImportError: cannot import name 'WhiteKernel'

Trying to run everest using the latest scipy (v1.0+) fails because they've moved it.

Need to change

from scipy.misc import comb

to

from scipy.special import comb

in the mathutils.py file.

How can I use this package to compute new k2 planet candidate? @rodluger