C8 K2 finds

• by ajamyajax

  Re 220162807: as of 7/1/2016 looks like the C8 files are ready.. So hopefully MAST data will be available from Al soon as well!

  And as before, I won't post about any more new candidates until LcTools users have data to work with also, but here is a sneak peek of an apparent eccentric binary in minimally corrected data. The first transit event is only partially visible, and may or may not appear in more corrected data because data reducing algorithms tend to truncate the beginning and ending parts of data they process, which is fairly typical for those routines.

  But that's fine, I'll keep an eye on that sort of stuff. 😃 And enjoy! (soon). Now I'm going back to work on C7 some more..

  s1=2559.245 p1=48.905 d1=0.85 (20.4 hours +/-)
  
  s2=2578.53 p2=48.905 d2=1.2 (28.8 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220162807 , 2MASS J01082323-0127108 , 9.963 , 9.567 , 9.452 , 0.396 , 0.115 , ('K0V', 0.89) , ('K3V', 0.81)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220162807 17.0969 -1.4530 0.07 11.273 8
  
  220161803 17.1008 -1.4850 116.05 17.698 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220162807,2MASS J01082323-0127108,17.096880,-1.453003,5287.00,3.09,0.92,11.273,-0.100,-14.800,472.2±775.6
  

  Listed as TYC 4681-1000-1 -- Star on Simbad, Proper motions mas/yr: -0.1 -14.8, 01 08 23.251 -01 27 10.81

  
  

  Posted July 1, 2016 6:31 PM

• by Shellface

  Huzzah! (I'm on time for once!)

  Campaign 8 lies around the border between Pisces and Cetus. It is mostly devoid of notable objects, but is still well-suited for planet detections.

  Uranus also lies close to the centre of the field. As it is quite bright it may contaminate some nearby stars, but it should not be severe beyond a few arcminutes.

  So far as I can tell, the only already known transiting planet host is EPID 220303276. This is either WASP-107 or WASP-118, neither of which have yet been published.

  Posted July 1, 2016 6:50 PM

• by zoo3hans

  Oh, this is unfotunate. I expected the data around the 24th June, now I'm leaving for 14 days holidays. So this probably means I will only be able to look for over-looked candiadtes then. Sigh...

  Posted July 1, 2016 8:19 PM

• by ajamyajax in response to zoo3hans's comment.

  Dear Hans Martin,

  Always plenty to do later with K2 and beyond, so no worries my friend. Have a wonderful holiday vacation! We will be here when you return. 😃

  Best Regards, Mark

  Posted July 1, 2016 11:45 PM

• by zoo3hans

  EPIC 220303276 is WASP-118b, a hot Jupiter in a 4.047 day orbit around an F6 star (GO8060 Program).

  

  Posted July 2, 2016 8:19 AM

• by zoo3hans

  Probable glitch area in K2-C8: BKJD 2591.25.

  EPIC 220303143

  

  EPIC 220303197

  

  EPIC 220303025

  

  Posted July 2, 2016 9:04 AM

• by zoo3hans

  EPIC 220303659, EB with P=1.366 days, V-shaped.

  

  Posted July 2, 2016 9:40 AM

• by zoo3hans

  EPIC 220302728, EB with P=3.853 days.

  

  Posted July 2, 2016 12:38 PM

• by ajamyajax

  C8 also has IC1613:
  

  From http://keplerscience.arc.nasa.gov/K2/Fields.shtml

  "IC 1613 (also known as Caldwell 51) is an irregular dwarf galaxy..."
  
  "IC 1613 is a member of the Local Group. It has played an important role in the calibration of the Cepheid variable period luminosity relation for estimating distances. Other than the Magellanic Clouds, it is the only Local Group dwarf irregular galaxy where RR Lyrae-type variables have been observed..."
  

  "IC 1613 contains a WO star (edit Wolf–Rayet star, spectral class O) known as DR1, the only one so far detected further away than the Magellanic Clouds.."
  

  From https://en.wikipedia.org/wiki/IC_1613
  

  https://en.wikipedia.org/wiki/Wolf–Rayet_star

  Posted July 2, 2016 6:24 PM

• by Artman40

  http://keplerscience.arc.nasa.gov/k2-campaign-8-data-available.html

  K2 campaign data officially available on MAST archive.

  "Long cadence light curves, target pixel files, and full frame images for K2 Campaign 8 are now available for download from the K2 data archive at MAST. The data are not yet searchable using the K2 data search interface, which will be available later this week.

  The Campaign 8 target list included 24187 standard long cadence and 54 short cadence targets.

  In addition, the campaign included several custom masks:

  The planet Uranus was observed for roughly a month in short cadence, and the remaining time in long cadence.

  Four irregular Uranian satellites were observed in long cadence over a period of one month (Caliban, Sycorax, Prospero, Setebos).

  Six Hilda asteroids were observed in long cadence (1999 TJ90, 1999TS40, 1999 VG135, 2000 WC140, 2006 UB219, 2007 RY194).

  Four Trans-Neptunian Objects (TNOs) were observed in long cadence (1998 SN165, 2001 QT322, 2003 QW90, 2005 RS43).

  The irregular dwarf galaxy IC 1613 was covered using a 120-by-160 pixel mask.

  Finally, we covered several very bright stars using custom pixel masks that collect the wings of the PSF."

  By the way, do those custom pixel masks used to observe Solar System objects also have some stars to be analyzed?

  In the moment I'm typing this, Campaign 9 data is being downlinked.

  Posted July 4, 2016 9:08 PM

• by Artman40

  http://arxiv.org/abs/1607.00774

  "WASP-92b, WASP-93b and WASP-118b: Three new transiting close-in giant planets"

  What's important is the WASP-118b which is in Kepler field of view and probably a target as well.
  Also, WASP-118b is at the ideal brightness for Kepler observations (about 11).

  Posted July 5, 2016 4:03 AM

• by Dolorous_Edd

  PC's EPIC :

  220231331 - I reconsidered, this could be well be a gas giant around M dwarf

  220282718 - period 0.278; eb?

  220397060 - period 12.132d; start at 2570.21

  220376054 - period 8.597d ; start at 2563.58

  220316844 - period 0.672d; eb perhaps

  220294712 - period 23.650; start at 2580.70

  220292715 - 2 transits ; p = 41.528; start at 2574.49

  220282533 - transits with 0.5d period; Eb perhaps ( and I somehow messed up EPIC number, damn have to find it again )

  220228500 - dips with 2.5d period; start at 2567.47 ; hard to tell but maybe there are additional dips i.e. 2584.66 and 2604.24

  220211593 - single dip at 2599.87

  220209578 - 2% drop likely EB

  220196638 - dips with ~56d period? start 2560.65

  220192485 - ~1% drop at 2576.23 second mabye at 2626.89 incomplete

  220187745 - maybe dip at 2597.80

  220176739 - maybe dip at 2563.5

  220172515 - mabye dip at 2627.44

  220167440 - maybe single dip at 2598.12

  220165972 - dips at 2574.35 and 2591.27 ?

  220151591 - hard to tell, maybe dips at 2600.8 and 2603

  220152847 - single dip 2568.84

  220161976 - maybe dip 2596.37

  EB's EPIC:

  220247484

  220222439 - maybe

  220204960 - shallow depth

  220204885

  220431824 - maybe eb or pc

  220421090

  220414426

  220410458

  220398184

  220382636

  220373025

  220370605

  220352451 - single transit at 2595.39

  220352059

  220351987

  220349319

  220345441

  220342646

  220339564

  220336320

  220320211

  220315635

  220314572

  220314481

  220314326 - maybe

  220314321

  220305504

  220304223

  220303977

  220300584

  220230146

  220297500

  220295586

  220294180

  220288894 - maybe

  220287920

  220287868

  220283604

  220282533

  220271452

  220258394

  220263105

  220257938

  220249541

  220243443

  220237951 - maybe

  220233302 - maybe

  220232512

  220231331 - single dip at 2601.76

  220228955

  220250469 - maybe something with 0.2d period

  220225167

  220223560

  220222060

  220207737

  220215954

  220220825

  220227021

  220214860

  220220139

  220219177

  220209683

  220209177

  220211491 - maybe single dip at 2615.59

  220201207 - shallow depth EB most likely

  220209177

  220208795 - maybe incomplete single dip at 2575.94

  220198860

  220196587

  220194833 - maybe drop at 2582.4

  220190173 single dip at 2584.43

  220187677 - single dip at 2585.37

  220187552 - 3% drop, eb perhaps

  220186803

  220182985

  220181625

  220180957 - maybe

  220180327

  220173169

  220142950 - EB??

  220161287 - EB?

  220162807 - EB with small dip at 2604.23

  220170815

  220171401

  220179606

  Other EPIC:

  220214615 - pulsation maybe EB

  220329972 - maybe dip at 2593.79: (maybe glitch )

  220224995 - empty space at coordinates

  229228826 - dip to the floor 2579.87

  220615486 - maybe CV

  220187843 - maybe dip 2599

  220171396 - regular pulsation

  220179717 - 2 long dips at beginning

  220182636 - sudden fall at the end

  220208664 - maybe dips with 18.3d period ; start at 2592.68

  220251335 - maybe single dip at 2561.70

  220298366 - maybe single dip at 2627.42

  220245523 - maybe single dip at 2606.19

  220306048 - maybe single dip at 2633.55

  220318540 - maybe dip at 2627.62

  220321605 - maybe dip at 2605.83

  220324054 - maybe dip at 2636.26

  220324654 - maybe dip at 2627.44

  220336147 - maybe dips at 2593.79 and 2633.02

  220348811 - maybe dip at 2567.31

  220358193 - something with 0.8d period

  220370605 - maybe dip at 2567.35

  220390770 - wierd drops

  220395416 - dip at 2574.5 also 2593.8

  220395864 - maybe dips at 2604.294 and 2579.28

  220401506 - just variable

  220411705 - incomplete drop at 2636.30

  220422244 - a bit wierd variable

  220211973 - variable

  220216730 - maybe dip at 2636.74

  Wierd flares EPIC:

  220329764

  220252567

  220131668

  220133060

  220137654

  220142089

  220149324

  220153235

  220206204 - lens?

  220201542

  220204076

  220212481

  220215306 - sort of low flux outburst

  220234622

  220236264 - sort of low flux outburst

  220374480

  220375370

  220377669

  220378662

  220382505

  220384033

  220384529

  220384809

  220390104

  220404032

  RR Lyr EPIC's:

  220383290

  220378583

  220359154

  220343343

  220340933

  220326597

  220325182

  220313822

  220308445

  220305336

  220289837

  220288040

  220280760

  220277833

  220271165

  220262484

  220262425

  220254538

  220253247

  220244829

  220242787

  220235122

  220229719

  220198696

  220198467

  220192221

  220191991

  220190195

  220181683

  220161256

  220146083

  Posted July 6, 2016 1:13 PM

• by Dolorous_Edd

  EPIC 220386321 - LC doesn't make sense;

  processing artifact? present also in Sap flux

  

  SAP_FLUX

  

  Posted July 6, 2016 3:32 PM

• by ajamyajax

  Re 220192485 from Ivan's list: an interesting early C8 target found by Ivan that could be a Saturn or a small stellar companion or even a brown dwarf. 0.78 R_sol estimate (Huber/NEA). There are two fairly complete transit events in the MC data, so that was used for this fit. But MAST fitted ok even with one partial transit. Also none of the nearby EPIC show any obvious sign of these transits, but Aladin Lite does show a possibly small nearby visual companion.

  s1=2576.225 p1=50.692 d1=0.19167 (4.6 hours or more)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220192485 , 2MASS J01163136-0017241 , 10.463 , 10.084 , 9.947 , 0.379 , 0.137 , ('G9V', 0.91) , ('K6V', 0.7)
  

  Semi-Major Axis a (A.U.) = 0.254
  
  Stellar diameter ratio = 0.78
  
  Stellar mass ratio = 0.85
  
  Period ~= 50.715 days
  
  Duration ~= 4.601 hours
  
  Estimated duration for center of star transit ~= 5.543 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220192485 19.1307 -0.2900 0.16 11.758 8
  
  220192748 19.1415 -0.2806 51.64 16.292 8
  
  220192908 19.1161 -0.2739 78.37 15.866 8
  
  220191904 19.1205 -0.3132 91.09 12.563 8
  
  220191791 19.1383 -0.3174 102.21 17.880 8
  
  220192131 19.1631 -0.3035 126.29 18.56 8
  
  220191687 19.1610 -0.3211 156.19 15.269 8
  
  220192014 19.0845 -0.3085 179.11 12.424 8
  
  220192936 19.1793 -0.2730 185.40 15.900 8
  
  220193523 19.2066 -0.2496 309.60 18.515 8
  
  220192213 19.0413 -0.3001 323.88 18.776 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220192485,2MASS J01163136-0017241,19.130703,-0.290045,5164.00,0.78,0.85,11.758,1.600,-12.600,156.1±15.06
  

  Listed as TYC 4682-800-1 -- Star on Simbad, Proper motions mas/yr: 1.6 -12.6, 01 16 31.369 -00 17 24.17

  Also from Simbad showing an interesting neighborhood, n arcsecs away. Note the low-mass star is not the nearby visual companion mentioned above.
  
  131.23: 2SLAQ J011622.74-001702.1 -- Quasar, 01 16 22.741 -00 17 02.16
  
  198.34: 2MASS J01162006-0019067 -- Low-mass star (M<1solMass), Spectral type: M5V, 1 16 20.06 -00 19 06.8
  
  205.54: SDSS-II SN 14821 -- SuperNova Candidate, 01 16 43.012 -00 19 12.36
  
  247.88: SDSS J011642.17-002031.5 -- Horizontal Branch Star, 01 16 42.177 -00 20 31.51
  

  

  Posted July 6, 2016 5:21 PM

• by JKD

  EPIC 220148816 Signal at 2599.47 BKJD, Period =?, Duration ~12.85 hrs, Depth ~2%

  EPIC 220152847 Signal at 2568.86 BKJD, Period =?, Duration ~12.95 hrs, Depth ~0.9% (mentioned by DE on page 2)

  EPIC 220177288 Signal at 2615.58 BKJD, Period =?, Duration ~1.96 hrs, Depth ~0,8

  EPIC 220177720 Signal at 2606.21 BKJD, Period =?, Duration ~4.41 hrs, Depth ~0.25%

  EPIC 220186159 Signal at 2585.97 BKJD, Period =?, Duration ~2.94 hrs, Depth ~12.5% (likely an EB-sgnal)

  EPIC 220187552 Signal at 2566.26 BKJD, Period =17.11days, Duration ~2.94 hrs, Depth ~2.7% (slightly eccentric signal, maybe another object around)

  EPIC 220187677 Signal at 2585.37 BKJD, Period =?; Duration ~2.45 hrs, Depth ~28.9% (maybe an EB-signal)

  EPIC 220192485 Signal at 2576.23 BKJD, Period =50.71 days, Duration ~4.90 hrs, Depth ~1% (Planet Candidate already mentioned by DE and ajamyajax )

  EPIC 200194833 Signal at 2582.44 BKJD, Period =?, Duration ~2.94 hrs, Depth ~1.4% (already mentioned by DE on page 2)

  EPIC 220195312 Signal at 2597.81 BKJD, Period =?, Duration ~15.2 hrs, Depth ~0.7%

  Posted July 8, 2016 7:37 AM

• by Dolorous_Edd

  PC's EPIC

  220471666 - period 8.267; start at 2561.32

  220471547 - period 0.274; EB perhaps

  220466136 - period 17.071; start at 2559.19

  EB's EPIC

  220271145

  220270444 - maybe

  220496837

  220495054 - maybe

  220490873

  220488981

  220485301

  220480814

  220479880

  220478413

  220477223

  220476633

  220475918 - maybe

  220474023

  220471927

  220468851

  220460233

  220460196

  220458522

  220453029

  220446493

  220443255

  220440299

  220434992

  220431824

  220429913

  RR Lyr's EPIC:

  220270196

  220497567

  220493201

  220489863

  220460648

  220455109

  220435063

  220432468

  220429650

  220424589

  Wierd flares EPIC's

  220468488

  220459259

  220468237

  220469567 - contaminated by Uranus

  Other EPIC's

  220469252 - maybe single dip at 2593.79

  220459861 - variable

  220475909 - maybe single dip at 2593.79

  220488370 - maybe dip at 2627.74 another at 2567.32

  Posted July 8, 2016 3:23 PM

• by ajamyajax in response to Dolorous_Edd's comment.

  Re 220386321's unusual artifact event: well there are a number of outbursts and spikes in C8 which could be any of the previously mentioned solar system objects and more. So identifying them all could be a daunting task. Using SkyboT helps, assuming its database is up to date, so maybe I'll have a list of possible solar system crossing objects for us at some point.

  This event is approx 5.9 days in duration and is centered ~2597.7 BKJD with a start ~2594.9 and ending ~2594.9. Nearby 220389374 and 220390104 have similar increases in flux around this time, but do look a little to a lot different. There are also several nearby natural phenomena which seem capable of producing unique outbursts anyway. AND there are supernovae in other C8 target neighborhoods, believe it or not.

  So a number of possible sources to consider including just spacecraft or processing glitches as Ivan mentioned. Hopefully we will figure out more as we go through C8.

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220386321 16.9082 4.4399 0.04 12.798 8
  
  220389374* 16.8664 4.5016 268.06 16.464 8
  
  220382505 16.8997 4.3632 277.80 18.455 8
  
  220390104* 16.8458 4.5160 353.88 15.691 8
  
  220381800 16.9483 4.3476 362.09 16.308 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220386321,2MASS J01073797+0426234,16.908212,4.439899,5699.00,0.98,1.00,12.798,0.900,-11.200,386.4±51.77
  
  220389374,2MASS J01072793+0430056,16.866383,4.501557,3674.00,0.28,0.30,16.464,-6.000,-30.000,164.6±41
  
  220382505,2MASS J01073592+0421474,16.899702,4.363194,,,,18.455,29.000,-56.000,
  
  220390104,2MASS J01072299+0430574,16.845812,4.515960,5827.00,0.93,0.85,15.691,3.200,-2.700,1597±797.8
  
  220381800,2MASS J01074759+0420515,16.948292,4.347648,3712.00,0.30,0.32,16.308,,,222.4±76.21
  

  Also from Simbad showing an interesting neighborhood, n arcsecs away:
  
  146.21: PMN J0107+0425 -- Radio-source, 01 07 46.60 +04 25 15.0
  
  156.09: HD 6698 -- Double or multiple star, Proper motions mas/yr: -15.69 -34.06, Spectral type: F5/6V, 01 07 46.40371 +04 24 51.7267
  
  394.16: [STK2001] 10979c -- gamma-ray Burst, 01 08 00.0 +04 30 00
  

  Posted July 8, 2016 4:27 PM

• by ajamyajax

  Re 220431824 from Ivan's list: a bit ragged, but using the 0.89 Huber/NEA value for R_sol a ~12.25Re planet candidate is possible here. However the longer duration for this period suggests the primary could be a larger star -- maybe even a giant or subgiant of 2.35 R_sol or so, which means a stellar companion instead.

  s1=2561.234 p1=9.0717 d1=0.28 (6.72 hours +/-)

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220431824 , 2MASS J00511854+0520004 , 11.776 , 11.381 , 11.311 , 0.395 , 0.07 , ('K0V', 0.89) , ('G1V', 1.07)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220431824 12.8273 5.3335 0.23 13.005 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220431824,2MASS J00511854+0520004,12.827252,5.333458,5446.00,0.89,0.97,13.005,9.100,-5.800,344.6±489.7(?)
  

  

  Posted July 8, 2016 4:31 PM

• by ajamyajax

  Re 220228500 from Ivan's list: looks fairly convincing as a sub-Neptune planet candidate, assuming the star is 0.75 R_sol (Huber/NEA).
  Also none of the nearby EPICs showed any obvious signs of this transit.

  s1=2559.97 p1=2.5044 d1=0.10 (2.4 hours +/-)

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220228500 18.5883 1.0047 0.02 13.422 8
  
  220228190 18.5686 0.9933 81.92 17.245 8
  
  220228653 18.5568 1.0093 114.60 18.443 8
  
  220228925 18.6225 1.0175 131.44 14.017 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220228500,2MASS J01142120+0100169,18.588302,1.004694,5246.00,0.75,0.80,13.422,26.100,18.800,338±55.47

  And from Simbad, n arcsecs away:
  
  149.30: SN 2006sd -- SuperNova, 01 14 24.155 +01 02 39.45
  
  169.44: 2MASS J01141032+0101030 -- Low-mass star (M<1solMass), Spectral type: M0V , 01 14 10.32 +01 01 03.0
  
  266.46: 2MASS J01143204+0056458 -- Low-mass star (M<1solMass), Spectral type: M4V, 01 14 32.04 +00 56 45.9
  
  290.22: 2MASS J01143601+0103234 -- Low-mass star (M<1solMass), Spectral type: M4V, 01 14 36.02 +01 03 23.4
  

  

  Posted July 8, 2016 4:32 PM

• by ajamyajax

  Re 220209578 from Ivan's list: this appears to be a small stellar companion because of the transit depth and the V-shaped fit. But a smaller star around ~0.77 R_sol produces a ~12.3Re radius estimate, so at least there is a chance for a planet candidate. Also none of the nearby EPICs show any sign of this transit, including the probably closer in distance star 220209709 which is only 18.6x arcsecs away visually. Fortunately, that is a K2 target also.

  s1=2561.765 p1=8.9047 d1=0.139167 (3.34 hours or more)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220209578 , 2MASS J01175088+0020311 , 13.221 , 12.904 , 12.850 , 0.317 , 0.054 , ('G5V', 0.98) , ('F6V', 1.25)
  
  220209709 , 2MASS J01175068+0020496 , 11.165 , 10.879 , 10.852 , 0.286 , 0.027 , ('G1V', 1.07) , ('B9.5V', 2.5)
  

  au min-max 0.075 0.085
  
  stellar diameter in solar units min-max 0.77 0.92
  
  stellar mass in solar units min-max 0.71 1.035
  
  period in days min-max 8.897 8.912
  
  duration in hours min-max 3.241 3.43
  

  Semi-Major Axis a (A.U.) = 0.08
  
  Stellar diameter ratio = 0.84
  
  Stellar mass ratio = 0.851
  
  Period ~= 8.909 days
  
  Duration ~= 3.3419 hours
  

  Semi-Major Axis a (A.U.) = 0.082
  
  Stellar diameter ratio = 1.05
  
  Stellar mass ratio = 0.94
  
  Period ~= 8.911 days
  
  Duration ~= 3.3406 hours
  
  Estimated duration for center of star transit ~= 4.0414 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220209578 19.4620 0.3420 0.07 14.376 8
  
  220209709 19.4612 0.3471 18.61 12.212 8
  
  220209167 19.4729 0.3274 65.54 15.322 8
  
  220209516 19.4952 0.3393 119.84 18.311 8
  
  220209793 19.4288 0.3505 123.44 14.384 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220209578,2MASS J01175088+0020311,19.462019,0.341995,5875.00,1.05,0.94,14.376,-5.700,-7.200,856.4±327.9
  
  220209709,2MASS J01175068+0020496,19.461155,0.347109,5984.00,1.24,1.09,12.212,-1.900,-34.300,392.4±86.81
  

  18.64 arcsecs away: TYC 20-749-1 -- Star on Simbad, Proper motions mas/yr: -1.9 -34.3, 01 17 50.677 +00 20 49.59
  

  

  Posted July 8, 2016 4:35 PM

• by Dolorous_Edd

  PC EPIC:

  220598367 - multiple signals; maybe EB or contamination

  220558588 - something wiht 0.355d period ; maybe EB

  220522262 - ~1.2% drop; period 8.689d

  220504338 - period 5.812d

  220501947 - 2% drop; period ~4.027 ; eb perhaps

  EB's EPIC:

  220592163

  220588267

  220588021 - 2% drop ; maybe eb

  220573494

  220571578

  220565349

  220562932

  220562140

  220559378

  220557951 - maybe

  220555968

  220553717

  220551856

  220551209

  220550457

  220549952

  220544669

  220544503

  220542353

  220541275

  220539163

  220527135 - maybe

  220522328

  220519942

  220516443

  220515668 - single transit at 2599.43

  220514093

  220513270

  220511803 - maybe just variable

  220507881

  220502355

  220501719

  220501059

  RR Lyr:

  220575441

  220545244

  220528452

  220518877

  220511999

  Other EPIC

  220531108 - dunno myabe HB

  220533965 - Outburst?

  220562046 - maybe dip at 2604.83

  Posted July 8, 2016 6:22 PM

• by Dolorous_Edd

  PC EPIC:

  220674823 - period 13.336d

  220643470 - period 2.653; i.e. 2600.61

  220629489 - period 1.921

  220606084 - maybe, one incomplete transit at 2618.27

  EB's EPIC

  229228946

  229228879 - maybe WD; 50% drop

  229228815

  229228814

  229228808

  229228807

  229228806

  229228483

  220741519 - depth changes; evolving orbit?

  220732672

  220731239

  220727924

  220727268

  220725183

  220720246

  220716106

  220712399 - maybe dips at 2602.99 and 2629.43

  220709506

  220691733

  220691721

  220689701

  220689083

  220688589

  220688043 - something with 0.444 period, maybe eb

  220684849

  220680367 - maybe

  220678893

  220678478 - maybe

  220674623

  220658946

  220655823

  220650789

  220638699

  220631539

  220629445

  220628834

  220620962

  220619415 - maybe EB; all transits are incomplete

  220611561

  220610892

  220610601

  220608301

  220607437 - maybe or just pulsating

  220605820 - single dip at 2590.86 in glitch area so not sure

  220604574 - maybe

  220604429 - single dip at 2600.75

  220603342

  Other EPIC

  220709978 - maybe dips 2581.46 and 2596.86

  220615486 - maybe CV

  RR Lyr EPIC:

  229228845 - Cepheid

  229228844 - Cepheid

  229228840 - Cepheid

  229228839 - Cepheid

  229228835 - Cepheid

  229228831 - Cepheid

  229228830 - Cepheid

  229228829 - Cepheid

  229228827- Cepheid

  229228826 - Cepheid

  229228825 - Cepheid

  229228824- Cepheid

  229228822- Cepheid

  229228821- Cepheid

  229228820 - Cepheid

  229228819

  229228818

  229228817

  229228816

  229228813

  229228812

  229228810

  229228809

  220721216

  220688027

  220654797

  220640471

  Posted July 8, 2016 10:22 PM

• by Dolorous_Edd

  EPIC 220422244 is clearly periodic variable, what type it is? just curious

  

  Posted July 9, 2016 10:34 AM

• by Shellface in response to Dolorous_Edd's comment.

  The star appears to be late-A - early-F (~7300 K), so I'm going to wager that the variability is heartbeat superimposed on Gamma Doradus.

  Posted July 9, 2016 3:10 PM

• by ajamyajax in response to Shellface's comment.

  [Agree about the HB, just finished working up some details to try and answer Ivan's question also; will post it as-is to save editing -- and move on to the next system, as I always do...]

  Re 220422244 from Ivan's list: I think this could be a heartbeat binary that will end up in a paper like the one below (and I have mentioned before). This system also appears to have A- to F-type primary stars like their common examples. The idea I believe, is these systems are eccentric configurations of hot stars that are tidally spun up when reaching periastron -- when the components of a binary system are nearest.

  And they could be non-transiting from our point of view too, so all we see are periodic changes in brightness. Also perhaps we can actually see the secondary increase in brightness with an eccentric timed transit as shown, which would be pretty neat if the case.

  So hope this helps. Only a few of us here now who find this all very interesting, which is too bad. But we press on...
  

  p.s. Also nearby 220420979 looks periodic in a Cepheid kind of way, with a different ~23.5 period. Will look at that one closer later.

  s1=2566.50 p1=7.57 d1=1.4 (33.6 hours +/-)
  
  s2=2464.94 p2=7.57 d2=0.20 (4.8 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220422244 , 2MASS J01033871+0508495 , 9.962 , 9.865 , 9.838 , 0.097 , 0.027 , ('A9V', 1.66) , ('B9.5V',2.5)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220422244 15.9113 5.1471 0.0 10.496 8
  
  220420979 15.9103 5.123 86.78 15.817 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220422244,2MASS J01033871+0508495,15.911337,5.147102,7198.00,1.67,1.53,10.496,20.300,-8.000,
  

  Listed as TYC 25-563-1 -- Star on Simbad, Proper motions mas/yr: 20.3 -8.0, 01 03 38.7161 +05 08 49.538

  Also per the Huber/NEA value, 7200K is an ~F0V type star, ~1.58 M_sol.

  "HEARTBEAT STARS: SPECTROSCOPIC ORBITAL SOLUTIONS FOR SIX ECCENTRIC BINARY SYSTEMS"
  
  http://arxiv.org/pdf/1506.06196v1.pdf

  
  

  Posted July 9, 2016 3:31 PM

• by ajamyajax

  Re 220420979: well I haven't looked at a lot of Cepheids yet, but this target appears periodic so perhaps it is a Type II Cepheid. It seems to fit the general Wiki description listed below. Also maybe its distance is greater than the current estimate because it is dim at 15.817 Kepmag, and therefore maybe larger in size. For example, my experimental log(g) program estimate is ~4.27 which puts this star over Sun size to conform with a confirmed data stellar radius curve that I use. But that is just one test. Also the nearby EPICs are not contaminating this light curve or vice versa.
  

  s1=2580.25 p1=23.55 d1=10.83 (260 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220420979 , 2MASS J01033847+0507229 , 13.750 , 13.120 , 12.947 , 0.63 , 0.173 , ('M8V', 0.082) , ('K7V',0.64)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220420979 15.9103 5.123 0.0 15.817 8
  
  220422244 15.9113 5.1471 86.78 10.496 8
  
  220419811 15.9208 5.1011 87.26 12.948 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220420979,2MASS J01033847+0507229,15.910334,5.123017,4033.00,0.46,0.52,15.817,8.700,-10.400,291.9±51.05
  

  "Type II Cepheids are variable stars which pulsate with periods typically between 1 and 50 days. They are population II stars: old, typically metal-poor, low mass objects."

  From: https://en.wikipedia.org/wiki/Type_II_Cepheid

  

  Posted July 9, 2016 8:10 PM

• by Dolorous_Edd

  Ah, thanks @Shellface and @ajamyajax

  I didn't recognize it.

  Re: 220420979

  IMO not a Cepheid just standard variable, dips 2564,8 MJD and 2591.1 MJD look kind of interesting

  Posted July 10, 2016 7:01 PM

• by ajamyajax

  Well, work continues.. This is my kind of thing though; just saw this paper:

  "FUNDAMENTAL PARAMETERS OF MAIN-SEQUENCE STARS IN AN INSTANT WITH MACHINE LEARNING"
  
  Earl P. Bellinger, George C. Angelou, Saskia Hekker, Sarbani Basu, Warrick H. Ball, and Elisabeth Guggenberger
  
  http://arxiv.org/pdf/1607.02137v1.pdf

  And I have a few more binaries to catch up on for C7, but I may disappear for stretches of time as I work on fascinating new algorithms like the above. 😃 GLTA

  Posted July 11, 2016 12:46 PM

• by ajamyajax

  Re 220294712 from Ivan's list: seems to work all right as a Neptune planet candidate if a 1.3 R_sol F-type star. Somewhat smaller works too.
  There is a bright visual neighbor in 220292272 but it is also a K2 target and shows no sign of this transit. Ditto with the other EPIC neighbors.
  

  s1=2580.717 p1=23.618 d1=0.28 (6.72 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220294712 , 2MASS J01123885+0231187 , 11.293 , 11.024 , 10.970 , 0.269 , 0.054 , ('G2V', 1.0) , ('F4V',1.37)
  

  Semi-Major Axis a (A.U.) = 0.163
  
  Stellar diameter ratio = 1.3
  
  Stellar mass ratio = 1.028
  
  Period ~= 23.62 days
  
  Duration ~= 6.7213 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220294712 18.1619 2.5219 0.09 12.264 8
  
  220292272 18.1277 2.4716 218.83 6.488 8
  
  220293034 18.2151 2.4871 228.66 13.049 8
  
  220291739 18.1408 2.4601 234.98 15.037 8
  
  220295711 18.2270 2.5417 244.77 18.080 8
  
  220297095 18.1109 2.5684 248.38 11.192 8
  
  220297989 18.1948 2.5861 259.73 12.359 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220294712,2MASS J01123885+0231187,18.161898,2.521875,6073.00,1.21,1.05,12.264,-6.700,-19.000, 417.6±97.33
  

  

  Posted July 11, 2016 12:48 PM

• by JKD

  EPIC 220196587 already marked by DE as a PC on page 2.
  However, there are 2 different repeating signals with similar duration and period.

  S1 at 2563.34 BKJD, Period ~11.38 days, Duration ~5.39 hrs, Depth ~2.2%

  S2 at 2569.46 BKJD, Period ~11.39 days, Duration ~4.90 hrs, Depth ~0.1%

  Posted July 13, 2016 7:45 PM

• by ajamyajax

  Re 220471666 from Ivan's list: some blending, but could be a mini gas giant planet candidate using the Huber/NEA value of 1.18 R_sol.
  

  s1=2561.33 p1=8.27 d1=0.10 (2.4 hours +/-)

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220471666 , 2MASS J01135281+0607261 , 11.679 , 11.405 , 11.298 , 0.274 , 0.107 , ('G2V', 1.0) , ('K2V',0.85)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220471666 18.4701 6.1239 0.0 12.798 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220471666,2MASS J01135281+0607261,18.470087,6.123902,5827.00,1.16,1.08,12.798,-8.000,-9.900,
  

  

  Posted July 13, 2016 9:56 PM

• by ajamyajax

  Re 220196587 from Ivan's list and JKD's mention: I think JKD is right about the transits, and this is a slightly eccentric binary. The primary transit is shown; the secondary is very small but has visible repeats.
  

  s1=2563.36 p1=11.3885 d1=0.1933 (4.64 hours +/-)
  
  s2=2569.468 p2=11.3885 d2=0.1933 (4.64 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220196587 , 2MASS J00551372-0007541 , 9.899 , 9.613 , 9.534 , 0.286 , 0.079 , ('G1V', 1.07) , ('G5V',0.98)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220196587 13.8072 -0.1317 0.0 10.922 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220196587,2MASS J00551372-0007541,13.807215,-0.131667,5960.00,1.22,1.08,10.922,37.800,-14.100,
  

  

  Posted July 13, 2016 9:58 PM

• by ajamyajax

  Re 220504338 from Ivan's list: this target looks like a fine sub-Saturn planet candidate in MC data using the 0.90 R_sol value from Huber/NEA.
  Also none of the nearby EPICs show any contamination.
  

  s1=2559.905 p1=5.815 d1=0.111 (2.66 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220504338 , 2MASS J01174783+0652080 , 12.347 , 11.998 , 11.949 , 0.349 , 0.049 , ('G8V', 0.94) , ('F1V',1.5)
  

  Semi-Major Axis a (A.U.) = 0.062
  
  Stellar diameter ratio = 0.9
  
  Stellar mass ratio = 0.92
  
  Period ~= 5.822 days
  
  Duration ~= 2.6613 hours
  
  Estimated duration for center of star transit ~= 3.0275 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220504338 19.4493 6.8689 0.0 13.514 8
  
  220503881 19.4460 6.8596 35.46 16.094 8
  
  220505115 19.4628 6.8853 76.4 12.755 8
  
  220505371 19.4393 6.8902 84.77 11.386 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220504338,2MASS J01174783+0652080,19.449286,6.868895,5633.00,0.90,0.92,13.514,22.300,-15.800,
  

  
  

  Posted July 13, 2016 10:00 PM

• by Dolorous_Edd

  Re 220196587 hence that's why it was in the EB list in the first place

  EPIC:220196585

  There is a visible companion the east, maybe it is EB after all

  UKIRT J-band

  

  CFHT I2 band image

  

  Posted July 14, 2016 10:13 AM

• by Dolorous_Edd

  EPIC 220228500

  UKIRT J-band

  

  Subaru W-J-VR

  

  Posted July 14, 2016 10:30 AM

• by Dolorous_Edd

  EPIC 220504338

  UKIRT J-band

  

  CFHT G-band

  

  Posted July 14, 2016 10:40 AM

• by JKD

  EPIC 220206243 on other signal around 2580.xx BKJD

  Period =?, Duration ~44.1 hrs, Depth ~0.18%

  EPIC 220208795 already marked by DE on page 2 as a pot. PC (correction EB)

  Signal at 2575.94 BKJD, Period =?, Duration N 4.90 hrs, Depth ~15.4%

  EPIC 220209578 already mentioned by DE and ajamyajax;

  supporting the idea of a close PC, Period ~8.90 days, Duration ~3.45 hrs, Depth ~2.3%

  Posted July 14, 2016 8:40 PM

• by Dolorous_Edd

  EPIC 220294712

  UKIRT J-band

  1' x 1'

  

  Posted July 15, 2016 11:36 AM

• by Dolorous_Edd

  EPIC 220471666

  UKIRT K-band

  

  CFHT G-band

  

  Posted July 15, 2016 11:50 AM

• by Dolorous_Edd

  EPIC 220598367 - Trinary?

  nearby star is EPIC 220598410

  UKIRT J-band

  1'x1'

  

  CFHT G-band

  

  Posted July 15, 2016 10:36 PM

• by ajamyajax

  Re 220501947 from Ivan's list: very sparse transit data but even with that, seems to work ok as a large gas giant planet candidate up to 0.80 R_sol (or so). And MC data used again for this fit because the transits are more even than the MAST conversion. Also the Huber/NEA value of 0.63 R_sol produces an ~9.71Re PC radius estimate. Of course this could be a binary. However none of the nearby EPICs show any obvious sign of this transit.
  

  s1=2562.42 p1=4.02465 d1=0.10 (2.4 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220501947 , 2MASS J01182635+0649004 , 11.807 , 11.259 , 11.135 , 0.548 , 0.124 , ('K4V', 0.78) , ('K3V',0.81)
  

  au min-max 0.04 0.05
  
  stellar diameter in solar units min-max 0.645 0.87
  
  stellar mass in solar units min-max 0.525 1.03
  
  period in days min-max 4.024 4.034
  
  duration in hours min-max 2.309 2.5
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220501947 19.6099 6.8169 0.0 13.539 8
  
  220502147 19.6139 6.8217 22.55 15.773 8
  
  220501813 19.5725 6.814 134.22 14.270 8
  
  220501973 19.5705 6.8176 141.0 15.419 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220501947,2MASS J01182635+0649004,19.609899,6.816871,4476.00,0.62,0.69,13.539,55.200,-34.200,
  

  

  Posted July 16, 2016 12:28 PM

• by ajamyajax

  Re 220674823 from Ivan's list: seems to fit ok for a mini gas giant planet candidate. 0.83 R_sol estimate used here, but a range in this area also works. Also the nearby EPIC does not show any sign of this transit.
  

  s1=2559.409 p1=13.339 d1=0.154167 (3.7 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220674823 , 2MASS J00521914+1047409 , 10.770 , 10.454 , 10.344 , 0.316 , 0.11 , ('G5V', 0.98) , ('K4V',0.78)
  

  Semi-Major Axis a (A.U.) = 0.106
  
  Stellar diameter ratio = 0.83
  
  Stellar mass ratio = 0.905
  
  Period ~= 13.344 days
  
  Duration ~= 3.7015 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220674823 13.0798 10.7947 0.0 11.958 8
  
  220675843 13.1044 10.8209 128.27 15.771 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220674823,2MASS J00521914+1047409,13.079780,10.794699,5814.00,0.99,0.94,11.958,58.200,2.700,
  

  

  Posted July 16, 2016 12:29 PM

• by ajamyajax

  Re 220643470 from Ivan's list: this target listed with a giant or subgiant star, but maybe only ~1.6 R_sol in size if this transit is close to the equator.
  Or could be a blend from another source. But if the transit belongs to this star it looks like a planetary fit that could be super-Neptune size or greater. There might be a blended secondary but the early data is ragged there. At least neither of the nearby EPICs show an obvious sign of this transit.
  

  s1=2560.815 p1=2.653 d1=0.1358 (3.5 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220643470 , 2MASS J00493540+1001123 , 9.026 , 8.330 , 8.229 , 0.696 , 0.101 , ('M8V', 0.082) , ('K3V',0.81)
  

  au min-max 0.04 0.045
  
  stellar diameter in solar units min-max 1.44 1.72
  
  stellar mass in solar units min-max 1.205 1.74
  
  period in days min-max 2.643 2.662
  
  duration in hours min-max 3.401 3.597
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220643470 12.3976 10.0201 0.0 10.839 8
  
  220643369 12.3816 10.0175 57.18 12.634 8
  
  220644688 12.3772 10.0495 128.19 15.435 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220643470,2MASS J00493540+1001123,12.397556,10.020078,4409.00,22.34,0.95,10.839,-18.000,-9.700,
  

  

  Posted July 16, 2016 12:30 PM

• by ajamyajax

  Re 220629489 from Ivan's list: this transit appears to be stellar, so perhaps a blended binary more likely. But even at ~1.2 R_sol a grazing gas giant is somewhat possible. Also none of the nearby EPICs show any obvious sign of this transit.
  

  s1=2559.99 p1=1.9206 d1=0.1033 (2.48 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220629489 , 2MASS J00524666+0941345 , 12.579 , 12.114 , 11.983 , 0.465 , 0.131 , ('K2V', 0.85) , ('K6V',0.7)
  

  au min-max 0.03 0.035
  
  stellar diameter in solar units min-max 1.045 1.325
  
  stellar mass in solar units min-max 0.97 1.565
  
  period in days min-max 1.912 1.93
  
  duration in hours min-max 2.382 2.579
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220629489 13.1944 9.6929 0.10 14.119 8
  
  220629125 13.1979 9.6845 32.75 13.518 8
  
  220628013 13.2317 9.6590 180.07 15.634 8
  
  220631639 13.2282 9.7405 209.06 15.652 8
  
  220632257 13.1931 9.7547 222.44 12.846 8
  
  220628196 13.2597 9.6632 255.20 10.863 8
  
  220631011 13.2887 9.7261 355.25 11.073 8
  
  220625341 13.2301 9.6001 357.36 16.439 8
  
  220633919 13.1860 9.7936 363.66 13.328 8
  
  220624940 13.2400 9.5898 404.97 10.547 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220629489,2MASS J00524666+0941345,13.194414,9.692924,4957.00,0.76,0.82,14.119,-17.100,-3.600,
  

  

  Posted July 17, 2016 12:33 PM

• by ajamyajax

  Re 220397060 from Ivan's list: this target's giant or subgiant star radius gets some support from the transit period and duration. However the mass seems even larger, so perhaps this suggests more of a binary. A U-shaped fit for this transit, but also a fairly large radius estimate of 19Re for the transiting object. And the nearby EPIC does not show any sign of contamination.
  

  s1=2570.208 p1=12.10 d1=0.35 (8.4 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220397060 , 2MASS J00344732+0439279 , 11.559 , 11.087 , 11.027 , 0.472 , 0.06 , ('K2V', 0.85) , ('F7V',1.21)
  

  Semi-Major Axis a (A.U.) = 0.154
  
  Stellar diameter ratio = 3.0
  
  Stellar mass ratio = 3.315
  
  Period ~= 12.1 days
  
  Duration ~= 8.4004 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220397060 8.6972 4.6578 0.0 12.835 8
  
  220397008 8.7123 4.6565 54.55 10.791 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220397060,2MASS J00344732+0439279,8.697182,4.657757,5099.00,3.00,0.90,12.835,-12.800,-6.100,
  

  

  Posted July 17, 2016 12:34 PM

• by ajamyajax

  Re 220376054 from Ivan's list: this target could have a decent mini gas giant planet candidate, and with a near Sun-size star of 0.99 R_sol.
  

  s1=2563.587 p1=8.60 d1=0.1542 (3.7 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220376054 , 2MASS J00593025+0413402 , 10.576 , 10.217 , 10.223 , 0.359 , -0.006 , ('G8V', 0.94) , ('B6V',4.0)
  

  au min-max 0.07 0.09
  
  stellar diameter in solar units min-max 0.825 1.115
  
  stellar mass in solar units min-max 0.62 1.315
  
  period in days min-max 8.591 8.606
  
  duration in hours min-max 3.604 3.798
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220376054 14.8761 4.2278 0.0 11.597 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220376054,2MASS J00593025+0413402,14.876077,4.227798,5694.00,0.99,0.98,11.597,-28.900,-21.600,
  

  

  Posted July 17, 2016 12:36 PM

• by ajamyajax

  Re 220522262 from Ivan's list: in MAST data, another possible sub-Saturn to Saturn class planet transiting across a small K-dwarf. And the 0.66 R_sol Huber/NEA value used for this fit but a larger 0.8x radius produces more of a Saturn-sized PC estimate. Also nearby 220522541 has a few transit-looking features, but none seem aligned with those seen here.
  

  s1=2560.88 p1=8.688 d1=0.11 (2.64 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220522262 , 2MASS J01045457+0716093 , 13.195 , 12.626 , 12.523 , 0.569 , 0.103 , ('K6V', 0.7) , ('K2V',0.85)
  

  au min-max 0.065 0.075
  
  stellar diameter in solar units min-max 0.535 0.66
  
  stellar mass in solar units min-max 0.485 0.745
  
  period in days min-max 8.692 8.697
  
  duration in hours min-max 2.543 2.737
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220522262 16.2274 7.2692 0.0 14.763 8
  
  220522541 16.2409 7.2747 52.22 13.331 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220522262,2MASS J01045457+0716093,16.227351,7.269234,4598.00,0.66,0.73,14.763,22.800,-0.700,
  

  From Simbad, 217.00 arcsecs away: SLW J0104+0719 -- Double or multiple star, 01 04 49.4 +07 19 32

  

  Posted July 17, 2016 12:37 PM

• by zoo3hans

  Well, I'm back from my holidays in Mallorca (Spain) and as usual I start from the last one and work to the first one.

  I see that Ivan (DE) has done already most of it, but nevertheless I'll try my luck.

  Here you go with my K2_C8_Korr_candidates:

  PC's:

  EPIC 220186645 P=7.06 days, starting at BKJD 2563.50, depth 0.0006, duration about 6 hours.

  EPIC 220222029 Mentioned by DE as "Other", P=25.438 days, starting at BKJD 2568.14, depth 0.0015, duration about 4 hours.

  EPIC 220282718 Mentioned by DE, P=0.2775 days, starting at BKJD 2560.87, depth 0.0007, duration about 1.5 hours.

  EPIC 220288191 Mentioned by DE as an EB candidate, P=24.41 days, starting at BKJD 2583.32, depth 0.0019, duration about 3.5 hours.

  EPIC 220321605 Mentioned by DE, but P=9.795 days, starting at BKJD 2566.65, depth 0.0018, duration about 3.5 hours.

  EPIC 220431824 Mentioned by DE as an EB or PC candidate, P=9.073 days, depth 0.016, duration about 7.5 hours, U-shaped. (Also already analyzed by Mark on page 2.)

  EPIC 220466136 (mentioned by DE, but wrong period) P=17.1 days.

  EPIC 220487418 (mentioned by DE, but I disagree with the period) P=14.072 days, starting at BKJD 2562.0, depth 0.0007, duration about 6.5 hours.

  EPIC 220526079 P=30.04 days, starting at BKJD 2572.574, depth 0.003, duration about 3 hours.

  EPIC 220532414 It looks somehow contaminated though, P=1.965 days, starting at BKJD 2565.0, depth 9.005, duration about 7 hours.

  EPIC 220554210 P=4.169 days, starting at BKJD 2562.01, depth 0.0013, duration about 4 hours. Maybe a second planet with P2=27.245 days, starting at BKJD 2566.71, depth 0.0008, duration about 5 hours.

  EPIC 220555384 P=4.285 days, starting at BKJD 2569.05, depth 0.0004, duration about 2.5 hours.

  EPIC 220562610 Single transit at BKJD 2563.72, depth 0.0028, duration about 12 hours, U-shaped.

  EPIC 220571481 P=8.79 days, starting at BKJD 2568.37, depth 0.0009, duration about 2.5 hours.

  EPIC 220578571 Maybe long transit at BKJD 2599.0, depth 0.0004, duration about 1.46 days.

  EPIC 220583201 Maybe transit at BKJD 2594.0 and 2627.65, depth 0.06, duration about 11 hours.

  EPIC 220598367 (also mentioned by DE) P1=7.646 days, starting at BKJD 2563.67, depth 0.0035, duration about 3.5 hours, P2=5.275 days, at BKJD 2562.38, depth 0.0035, duration about 3 hours, P3=5.273 days, at BKJD 2570.57, depth 0.0025, duration about 3 hours, so maybe eccentric EB instead.

  EPIC 220605820 (also mentioned by DE) P=46.47 days, starting at BKJD 2590.89, depth 0.0135, duration about 6 hours.

  EPIC 220606084 (also mentioned by DE) Single transit at BKJD 2618.26, depth 0.005, duration 8.5 hours.

  EPIC 220621788 Although mentioned by DE, the period seems to be rather 13.685 days, starting at BKJD 2568.26, depth 0.00055, duration about 4 hours.

  EPIC 220665845 Maybe single transit at BKJD 2584.35, depth 0.0025, duration about 10 hours.

  EPIC 220666631 P=15.985 days, starting at BKJD 2572.73, depth 0.0006, duration about 6 hours.

  EPIC 220674823 (mentioned by DE with one planet) P1=13.336 days, starting at BKJD 2572.72, depth 0.0008, duration about 5 hours, P2=0.571 days, starting at BKJD 2561.01, depth 0.0004, duration about 2.5 hours. Now both planets are confirmed in https://arxiv.org/pdf/1611.00397v1.pdf

  EPIC 220679571 Maybe single transit at BKJD 2578.91, depth 0.0027, duration about 3 hours.

  EPIC 220696233 P=28.735 days, starting at BKJD 2568.98, depth 0.014, duration about 4 hours.

  EPIC 220709978 P=40.93 days, starting at BKJD 2585.83, depth 0.0012, duration about 8 hours.

  EPIC 220709978 P=15.39 days, starting at BKJD 2566.10, depth 0.0006, duration about 6.5 hours.

  EB's:

  EPIC 220448185 As already mentioned by DE, P=0.3643 days, slight chance for a PC maybe, depth 0.02, duration about 2 hours, maybe other dips as well.

  EPIC 220502773 Probably contamination, P=0.8614 days or half of it.

  EPIC 220712399 at BKJD 2561.463 (sec.), 2603.0 (sec.) and 2629.4365 (prim.), period 26.4365 days.

  EPIC 220725183 P=2.311 days (or double this value).

  EPIC 220727924 P=0.8257 days

  EPIC 220731239 P=0.3167 days

  EPIC 220732672 P=8.50583 days

  EPIC 220741519 P=0.4287 days

  EPIC 229228483 P=0.528 days

  EPIC 229228716 at BKJD 2582.29.

  EPIC 229228879 P=0.08502 days

  EPIC 229228815 Hm, now it looks not so good anymore, rather a PC if anything

  EPIC 229228939 at BKJD 2583.02

  RR_Lyrae:

  EPIC 220721216

  EPIC 229228809

  EPIC 229228810

  EPIC 229228812

  EPIC 229228813

  EPIC 229228816

  EPIC 229228817

  EPIC 229228819

  Other:

  EPIC 220187552 Mentioned by DE as an EB, and also by JKD, P=17.09 days, starting at BKJD 2566.32, depth 0.026, duration about 3 hours. I see no secondaries. Unfortunately now confirmed as a False-Positive, see https://arxiv.org/pdf/1710.03239.pdf

  EPIC 220649443 Interesting short and very deep drops, for example at BKJD 2579.4.

  EPIC 229228820 Maybe Cepheid

  EPIC 229228821 Maybe Cepheid

  EPIC 229228822 Maybe Cepheid

  EPIC 229228825 Maybe Cepheid

  EPIC 229228830 Maybe Cepheid

  Posted July 17, 2016 7:49 PM

• by Dolorous_Edd

  Re: EPIC 220709978 and EPIC 220712399 ( as EBs and other )

  Yeah, noted them during first pass ( page 3 )

  220709978 is inconclusive with two visible dips at 2581.46 and 2596.86

  220712399 likely EB with incomplete primary at 2629.43 and secondary at 2602.99

  Posted July 18, 2016 8:49 PM

• by Artman40

  http://arxiv.org/abs/1607.05248

  "Two Small Planets Transiting HD 3167"

  "
  We report the discovery of two super-Earth-sized planets transiting the bright (V = 8.94, K = 7.07) nearby late G-dwarf HD 3167, using data collected by the K2 mission. The inner planet, HD 3167 b, has a radius of 1.6 R_e and an ultra-short orbital period of only 0.96 days. The outer planet, HD 3167 c, has a radius of 2.9 R_e and orbits its host star every 29.85 days. At a distance of just 45.8 +/- 2.2 pc, HD 3167 is one of the closest and brightest stars hosting multiple transiting planets, making HD 3167 b and c well suited for follow-up observations. The star is chromospherically inactive and slowly rotating, ideal for radial velocity observations to measure the planets' masses. The outer planet is large enough that it likely has a thick gaseous envelope which could be studied via transmission spectroscopy. Planets transiting bright, nearby stars like HD 3167 are valuable objects to study leading up to the launch of the James Webb Space Telescope."

  So basically , a star with V-magnitude brighter than 9, including 1 super-Earth and 1 almost Neptune-sized planet.

  So a bit more than 2 weeks from the MAST data release to the submission of this paper.

  Posted July 19, 2016 3:17 AM

• by Dolorous_Edd

  HD 3167 is EPIC 220383386

  Posted July 19, 2016 7:19 AM

• by ajamyajax in response to zoo3hans's comment.

  Oh yeah, and welcome back Hans Martin!!!

  Posted July 19, 2016 9:03 PM

• by ajamyajax

  Re 220598367 from Ivan's list and HM's mention: this interesting target is also a tough one.. The three transits pointed out by Hans Martin seem blended with one eccentric pair, but there could be as many as four small dwarfs in a bound system based on the fits. Note the two EPICs noted by Ivan as companions do indeed appear bound by the proper motion and distance estimates shown here. And there are no obvious contamination in the other nearby EPICs.
  

  s1=2563.70 p1=7.6415 d1=0.10 (2.4 hours +/-)
  
  s2=2562.395 p2=5.274 d2=0.09 (2.16 hours +/-)
  
  s3=2560.02 p3=5.274 d3=0.09 (2.16 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220598367 , 2MASS J01092804+0859180 , 12.757 , 12.349 , 12.222 , 0.408 , 0.127 , ('K2V', 0.85) , ('K4V',0.78)
  
  220598410 , 2MASS J01092734+0859221 , 12.983 , 12.537 , 12.463 , 0.446 , 0.074 , ('K3V', 0.81) , ('G3V', 1.0)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220598367 17.3668 8.9883 0.0 14.127 8
  
  220598410 17.3639 8.9894 11.07 14.330 8
  
  220597744 17.3902 8.9745 96.69 13.358 8
  
  220599758 17.3349 9.0197 160.21 9.323 8
  
  220596608 17.4137 8.9501 216.08 13.650 8
  
  220601399 17.3791 9.0568 250.40 11.212 8
  
  220599624 17.4435 9.0168291.26 13.635 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220598367,2MASS J01092804+0859180,17.366835,8.988306,5335.00,0.83,0.86,14.127,-0.900,-18.700,486.4±585.6
  
  220598410,2MASS J01092734+0859221,17.363944,8.989450,5215.00,0.79,0.82,14.330,1.700,-22.500,502.5±119.7
  

  From Simbad 95.43 arcsecs away, 2MASS J01093022+0857481 -- Possible Active Galaxy Nucleus, 01 09 30.222 +08 57 48.13

  
  
  

  Posted July 20, 2016 4:15 PM

• by zoo3hans

  K2_C8_Corr data is now available from Andrew Vanderburg via Al Schmitt's excellent LcViewer.

  Posted July 20, 2016 9:00 PM

• by Dolorous_Edd

  PC EPIC:

  220299658 - period 21.974; start at 2562.48

  220280237 - single dip at 2621.15 ; ~1.5% drop

  220250469 - from page 2 ; likely EB

  220221272 - period 13.625; start at 2573.21; well maybe

  220218012 - maybe PC; period 12.487d; start at 2570.6

  220216730 - period 18.276; start at 2581.89

  220198551 - something with 0.8d period?

  220180311 - something with 0.309d period

  220709978 - period 15.378, now looks solid

  EB EPIC

  220288191 - 2 dips ; 24.4d; 2583.33

  220232626

  220231755

  220231331 - now with more transits?

  220220200

  220231331 - now looks good

  220209167 - maybe single drop at 2604.37

  220208795 - single drop. now looks good

  220191598

  Others: (to sort later)

  220209516 - dip 2604

  220198080 - single dip at 2600.50

  220140752 - dip at 2574.41

  220141896

  220142011

  220147333

  220147984 - possible EB

  220148747

  220155078

  220156165

  220162424 - dip 2612

  220168551 - dip 2570

  220170512 - dip 2594

  220171524 - maybe EB

  220171907 - maybe dip 2607

  220186865 - 2571.69

  220190077 - maybe dip at 2596.80

  220192828 - dip at 2583.35

  220192855 - 2 dips 2599.61

  220196139 - dip at 2593.87

  220200210 - dip at 2601.26

  220203521 - single dip at 2602.54

  220219257 - single dip at 2607.46

  220222029 - maybe dips

  220225216 - maybe dip at 2603

  220224502 - maybe dip 2615

  220232774 - dip 2630

  220234521 - maybe dip at 2607

  220234753 - maybe dip at 2572

  220240246 - maybe dip at 2592.00

  220240741 - maybe dip at 2612.81

  220243804 - maybe dip 2615

  220262735 - huge dip at 2568?

  220268159 - dip 2600?

  220270790 - maybe dip at 2616.7

  220311474 - Mira?

  Posted July 20, 2016 9:36 PM

• by ajamyajax

  Re 220709978 from Ivan's and Hans Martin's lists: looks ok as a mini gas giant planet candidate with the Huber/NEA 1.10 R_sol value. And relatively nearby with high proper motions and a low distance value.
  

  s1=2566.068 p1=15.386 d1=0.19 (4.56 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220709978 , 2MASS J01055095+1145123 , 8.423 , 8.169 , 8.105 , 0.254 , 0.064 , ('F9V', 1.14) , ('F9V',1.14)
  

  au min-max 0.11 0.135
  
  stellar diameter in solar units min-max 0.9 1.145
  
  stellar mass in solar units min-max 0.75 1.385
  
  period in days min-max 15.377 15.395
  
  duration in hours min-max 4.469 4.655
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220709978 16.4623 11.7534 0.0 9.443 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220709978,2MASS J01055095+1145123,16.462281,11.753423,5818.00,1.10,1.05,9.443,56.700,67.600,98.75±45.84
  

  Listed as BD+10 125 -- Star on Simbad, Proper motions mas/yr: 56.7 67.6, Spectral type: G0, 01 05 50.9503 +11 45 12.315

  

  Posted July 21, 2016 2:32 AM

• by ajamyajax

  Re 220216730 from Ivan's list: a bit blended, but also looks fine as a mini gas giant planet candidate. 0.82 R_sol fit estimate shown, but could be a bit larger. And the nearby EPICs do not show this transit.
  

  s1=2563.59 p1=18.287 d1=0.2 (4.8 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220216730 , 2MASS J00450151+0035357 , 11.439 , 10.991 , 10.918 , 0.448 , 0.073 , ('K2V', 0.85) , ('G2V',1.0)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220216730 11.2563 0.5933 0.0 12.826 8
  
  220215948 11.2468 0.5662 103.07 16.964 8
  
  220215797 11.2395 0.5611 130.7 17.825 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220216730,2MASS J00450151+0035357,11.256313,0.593257,5121.00,0.82,0.88,12.826,16.600,-16.500,255.3±610.5(?)
  

  

  Posted July 21, 2016 2:34 AM

• by Dolorous_Edd

  PC EPIC

  220395416 - period 45.471; start at 2574.89

  220391408 - period 16.943; 2% - drop; maybe EB ( listed as M-dwarf ; R_stellar ~0.2 )

  220386957 - maybe single incomplete dip at 2594.27

  20383386 - is HD 3167 - confirmed planets

  220321605 - period 9.872;

  220315458 - single dip at 2611.48

  220315508 - maybe, period 4.45; i.e. 2577 and 2595

  EB EPIC

  220364369 - 2 transits

  220363759 - something with 0.2d period

  220352451 - from page 2 ; now with secondary

  220322258 - maybe

  Other EPIC

  220390770 - from page 2 ; 2 wierd drops

  220317635 - maybe dip 2593

  220340831 - Mira?

  220353725 - single dip 2617

  Posted July 21, 2016 3:19 AM

• by Dolorous_Edd

  PC EPIC:

  220487418 - period 14.093

  220481411 - period 2.175

  220436208 - 5.236

  220400100 - period 10.795d

  EB EPIC

  220476361 - single dip at 2633.20

  220449970 - maybe

  220448185 - 0.36d period

  220411820 - single dip at 2636.26

  220405171 - possible source of contamination

  220402747 - maybe; 0.3d period

  220401610 - 70% drop for primary, mind your

  Contamination EPIC

  220407282

  220406609

  220406081

  220403820

  220403421 - 63d period

  220403377 - 63.512d period

  220402807 - ok. again 57.791 period, contamination?

  220400525 - 2 transits; period 57.873d

  Other EPIC

  220410372 - strange raise

  220438204 - single dip 2589

  220453225 - possible HB?

  220484242 - strange raise

  220491120 - maybe dip at 2564

  Posted July 21, 2016 4:54 AM

• by Dolorous_Edd

  PC EPIC:

  220598331 - period 10.590d ; start at 2569.6

  220592745 - period 11.134d ; start at 2751.5

  220579319 - maybe; period 19.669; i.e. 2623

  220562610 - single dip at 2563.68; ~1% drop; mybe ~8Re * Noted it during first pass (before HM note ) , but deleted it accidentally , hence has to restore it later

  220510874 - period 7.473

  220503236 - period 8.678

  EB EPIC

  220598410 same as 220598367

  220580269 - maybe

  220574720 - maybe

  220549025 - maybe

  220540678 - Huh? similiar to 220540626 ( possible HB )

  220540626 - Possible HB

  220503410 - maybe; period 0.431

  Other EPIC

  220549827 - single dip at 2571.5

  220573361 - single dip 2601.86 ( glitch, I think )

  Posted July 21, 2016 7:49 AM

• by Dolorous_Edd

  PC EPIC

  220709978 - now have good transits ; period 15.383

  220696233 - period 28.722; 1.5% drop ( maybe gas giant around M type star )

  220676213 - period ~5; start = 2574.13 ; EB most likely secondary visible

  220674823 - maybe MPC? S1= period 13.336d; S2 =0.5d

  220650843 - period 10.224; i.e. 2582.2

  220648214 - 2 transits ; period 29.412; start at 2583.6

  220644522 - 2 transits ; period 40.935; start at 2585.5

  220631484 - period 13.266

  220621788 - period 13.674

  220621087 - period 3.836

  220606084 - now believable transit at 2618.23

  220605820 - now with 2 transits; period 46.431; ~1.5% drop maybe EB

  EB EPIC

  220712399 - now have good transits

  220666988

  220619415 - now looks good

  220614659

  Other EPIC

  220611790 - maybe single dip at 2603.5

  220606317 - single dip 2564

  220625044 - maybe dip at 2576.51

  220673263 - maybe not glitch at 2597

  Posted July 21, 2016 10:52 AM

• by ajamyajax in response to Dolorous_Edd's comment.

  Re 220674823 as a multi-planet candidate from Ivan's and Hans Martin's second look: sure looks like it. Maybe 1.46Re with the previous 0.83 R_sol estimate.

  s1=2559.409 p1=13.339 d1=0.154167 (3.7 hours +/-)
  
  s2=2561.02 p2=0.5712 d2=0.0833 (2.0 hours +/-)
  

  

  Posted July 22, 2016 12:11 AM

• by ajamyajax

  Re 220218012 from Ivan's list: also looks good as a mini gas giant planet candidate with a 0.95 R_sol estimate. And nearby 220217317 doesn't have any obvious sign of this transit.
  

  s1=2570.643 p1=12.487 d1=0.17 (4.08 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220218012 , 2MASS J00464793+0038268 , 11.780 , 11.456 , 11.383 , 0.324 , 0.073 , ('G5V', 0.98) , ('G2V',1.0)
  

  au min-max 0.1 0.115
  
  stellar diameter in solar units min-max 0.9 1.08
  
  stellar mass in solar units min-max 0.855 1.3
  
  period in days min-max 12.481 12.493
  
  duration in hours min-max 3.998 4.18
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220218012 11.6997 0.6408 0.0 12.971 8
  
  220217317 11.7225 0.6152 123.38 16.345 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220218012,2MASS J00464793+0038268,11.699704,0.640796,5697.00,0.90,0.88,12.971,-11.600,-44.500,358.5±82.56
  

  

  Posted July 22, 2016 12:14 AM

• by ajamyajax

  Re 220292715 from Ivan's list: another relatively close system, and this one could have a super-Neptune planet candidate. Only two sparse transits as shown however and it is a partial V-shaped as you can see, so a blended binary is also possible.
  

  s1=2574.495 p1=41.547 d1=0.15 (3.6 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220292715 , 2MASS J01130741+0228483 , 10.759 , 10.290 , 10.205 , 0.469 , 0.085 , ('K2V', 0.85) , ('G8V',0.94)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220292715 18.2809 2.4801 0.0 12.213 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220292715,2MASS J01130741+0228483,18.280867,2.480111,4854.00,0.71,0.77,12.213,115.500,29.700,147.6±14.61
  

  

  Posted July 22, 2016 12:15 AM

• by ajamyajax

  Re 220204960 from Ivan's list: possible eccentric binary (or likely trinary) with most dramatic ETV here it seems. The transits are V-shaped and fairly shallow as Ivan noted. But the timing is bizarre, as the objects seems to separate in the middle of this LC and then close the gap again. I don't think I've ever seen anything like this. If anyone has any other ideas what this is, pls post.

  Edit: maybe the spacing reunion timing tells us something about the possible outer star's perturbing orbit (in a trinary model). And could the third star be a heavy mass object capable of perturbing two other stars this dramatically?..

  s1=2561.726 p1~=7.2871 d1=0.12 (2.88 hours +/-)
  
  s2=2562.49 p2~=7.2726 d2=0.15 (3.6 hours +/-)
  
  s3=2562.10 p3~=72.8 d3=? (unseen third object estimate marked at apastron where repeats; also 10x resonance?)
  

  Update: gap estimates included:
  
  ttv1 = [2561.726,2568.867,2574.993,2582.136,2589.45,2595.397,2605.756,2613.253,2620.18,2627.667,2634.597]
  
  ttv2 = [2562.49,2570.03,2576.915,2584.43,2591.26,2598.85,2608.674,2614.826,2621.944,2628.107,2635.216]
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220204960 , 2MASS J00483264+0010183 , 11.749 , 11.536 , 11.443 , 0.213 , 0.093 , ('F7V', 1.21) , ('K0V',0.89)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220204960 12.136 0.1718 0.0 12.665 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220204960,2MASS J00483264+0010183,12.136040,0.171821,,,,12.665,-0.100,-8.500,
  

  From Simbad. x arcsecs away:
  
  43.76: 2SLAQ J004832.30+001101.9 -- Quasar, 00 48 32.304 +00 11 01.95
  
  73.92: 2MASS J00483645+0009316 -- Low-mass star (M<1solMass), Proper motions mas/yr: -5.0 1.0, Spectral type: M5V, 00 48 36.45 +00 09 31.6
  

  [Update: images corrected]
  
  
  

  Posted July 22, 2016 12:18 AM

• by JKD

  EPIC 220219896 Signal at 2629.56 BKJD, Period =?, Duration ~7.35 hrs, Depth ~0.3%

  Posted July 22, 2016 6:19 AM

• by Dolorous_Edd

  EPIC 220204960

  In optical there is only one visible companion less than 1" away

  UKIRT J-band (left) / CFHT I2 band (right)

  

  Posted July 22, 2016 9:38 AM

• by Dolorous_Edd

  EPIC 220540678 and EPIC 220540626 share the same LC ( no wonder 220540626 is ~1" from 220540678)

  Judging by LC could be heartbeat binary

  

  But could the also be visual binary?

  

  Posted July 22, 2016 3:20 PM

• by Dolorous_Edd

  EPIC 220390770

  Has some weird looking transits, unsure why maybe processing issues, maybe star is faint, maybe contamination or whatever

  

  Whole LC

  

  Skyview

  CFHT R-band

  

  Below is EPIC 220390685

  Posted July 22, 2016 5:46 PM

• by ajamyajax in response to ajamyajax's comment.

  Hans Martin, sorry I missed your MPC comment on 220674823 for credit; just corrected. You both are way ahead of the rest of us, as usual! 😃

  Posted July 22, 2016 6:57 PM

• by zoo3hans in response to ajamyajax's comment.

  Dear Mark

  no problem, thanks. But I think YOU are the real professional here!

  Cheers, Hans Martin

  Posted July 22, 2016 8:29 PM

• by JKD

  EPIC 220220200 EB with P~3.97 days

  EPIC 220220412 Signal at 2572.839 BKJD, P=?, Duration ~2.94 hrs, Depth ~0.05%

  EPIC 22022206 EB with P~6.37 days

  Posted July 22, 2016 9:32 PM

• by ajamyajax

  Re 220220200 from Ivan's and JKD's lists: as mentioned, this target looks like a small dwarf binary system with a mean transit depth of ~2.32%. Also the nearby EPICs do not show any sign of these transits.
  

  s1=2562.714 p1=3.9694 d1=0.10 (2.4 hours +/-)
  
  s2=2560.729 p2=3.9694 d2=0.10 (2.4 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220220200 , 2MASS J00445116+0042524 , 13.862 , 13.142 , 13.076 , 0.72 , 0.066 , ('M8V', 0.082) , ('F9V',1.14)
  

  au min-max 0.03 0.035
  
  stellar diameter in solar units min-max 0.975 1.24
  
  stellar mass in solar units min-max 0.91 1.465
  
  period in days min-max 1.976 1.993
  
  duration in hours min-max 2.301 2.499
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220220200 11.2132 0.7146 0.0 15.872 8
  
  220219620 11.2284 0.6944 91.06 14.904 8
  
  220219559 11.2317 0.6925 103.67 12.355 8
  
  220220452 11.2444 0.7222 115.52 18.394 8
  
  220220577 11.1736 0.7266 148.92 14.608 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220220200,2MASS J00445116+0042524,11.213208,0.714567,4228.00,0.53,0.59,15.872,34.500,-7.500,
  

  

  Posted July 23, 2016 5:12 PM

• by ajamyajax

  Re 220696233 from Hans Martin's and Ivan's lists: this target seems to have a ~1.34% transit depth, but could still be a gas giant candidate with a small star estimate of ~0.5 R_sol (shown). Of course a blended binary is also possible, or even a brown dwarf. The two nearby EPICs do not show this transit.
  

  s1=2568.981 p1=28.735 d1=0.152 (3.65 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220696233 , 2MASS J01174602+1122067 , 13.150 , 12.437 , 12.286 , 0.713 , 0.151 , ('M8V', 0.082) , ('K5V',0.75)
  

  au min-max 0.13 0.15
  
  stellar diameter in solar units min-max 0.455 0.545
  
  stellar mass in solar units min-max 0.355 0.545
  
  period in days min-max 28.734 28.743
  
  duration in hours min-max 3.579 3.717
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220696233 19.4418 11.3686 0.0 15.540 8
  
  220695678 19.4259 11.3542 76.36 13.161 8
  
  220697426 19.4221 11.4015 137.29 17.211 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220696233,2MASS J01174602+1122067,19.441792,11.368589,3841.00,0.42,0.47,15.540,2.800,-18.000,
  

  

  Posted July 23, 2016 5:14 PM

• by ajamyajax

  Re 220621788 from Ivan's and Hans Martin's lists: this target looks convincing as a mini gas giant planet candidate, from a range of 0.8 R_sol (shown) to the Huber/NEA value of 0.98 R_sol, or a bit more. Also the nearby EPICs do not show any sign of contamination.
  

  s1=2568.26 p1=13.685 d1=0.1529 (3.67 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220621788 , 2MASS J00510476+0931003 , 10.582 , 10.230 , 10.161 , 0.352 , 0.069 , ('G8V', 0.94) , ('G2V',1.0)
  

  au min-max 0.09 0.115
  
  stellar diameter in solar units min-max 0.665 0.89
  
  stellar mass in solar units min-max 0.52 1.085
  
  period in days min-max 13.675 13.694
  
  duration in hours min-max 3.571 3.767
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220621788 12.7699 9.5168 0.0 11.752 8
  
  220621988 12.7641 9.5212 25.67 13.662 8
  
  220620984 12.7735 9.499 65.2 15.994 8
  
  220620521 12.7435 9.4884 138.78 15.659 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220621788,2MASS J00510476+0931003,12.769862,9.516806,5643.00,0.98,0.98,11.752,30.000,-10.600,
  

  From Simbad 534.50 arcsecs away: CRTS J005049.0+092259 -- Eclipsing binary of W UMa type (contact binary), 00 50 49.02 +09 22 59.5
  

  

  Posted July 23, 2016 11:12 PM

• by ajamyajax

  Re 220605820 from Ivan's and Hans Martin's lists: only two transit events, but this target looks stellar with a transit depth of ~1.42% and a larger star. That would be a ~13Re object transit with a Sun-sized estimate, and it could be larger. The distance estimate is far as well. Also this transit does not appear in any of the nearby EPICs.
  

  s1=2590.88 p1=46.477 d1=0.265833 (6.38 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220605820 , 2MASS J01033855+0909163 , 12.384 , 11.923 , 11.866 , 0.461 , 0.057 , ('K2V', 0.85) , ('F6V',1.25)
  

  au min-max 0.25 0.275
  
  stellar diameter in solar units min-max 0.95 1.075
  
  stellar mass in solar units min-max 0.965 1.285
  
  period in days min-max 46.467 46.478
  
  duration in hours min-max 6.285 6.465
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220605820 15.9106 9.1545 0.0 13.762 8
  
  220605455 15.9398 9.146 108.03 14.513 8
  
  220605366 15.8791 9.1443 117.89 13.439 8
  
  220604960 15.9426 9.1362 131.47 13.441 8
  
  220604756 EXTENDED 15.88191 9.13145 x 15.31 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220605820,2MASS J01033855+0909163,15.910609,9.154469,5089.00,3.47,0.92,13.762,0.900,-4.300,1706±2330
  

  

  Posted July 23, 2016 11:13 PM

• by JKD

  EPIC 220222858 Signal at 2613.35 DKJD, P =?, Duration ~1.96 hrs, Depth ~3%

  Posted July 24, 2016 9:14 PM

• by ajamyajax

  Re 220390770 from Ivan's list: this target appears to be a longer period eccentric small dwarf binary with transit depths of ~6.95% and 4.83%. Transits still somewhat ragged as noted, but look more conventional in min corrected data as seen in this fit of the secondary. There is a nearby visual companion as seen on Aladin Lite.
  

  s1=2584.273 p1=? d1=0.9167 (22.0 hours +/-)
  
  s2=2611.12 p2=? d2=1.02 (24.5 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220390770 , 2MASS J01075500+0431440 , 13.464 , 12.850 , 12.710 , 0.614 , 0.14 , ('K6V', 0.7) , ('K5V',0.75)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220390770 16.9791 4.5289 0.0 15.367 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220390770,2MASS J01075500+0431440,16.979148,4.528943,4300.00,0.53,0.58,15.367,5.000,11.100,
  

  

  Posted July 26, 2016 2:54 PM

• by ajamyajax

  Re 220540678 and 220540626 from Ivan's list: and as Ivan identified, these LCs look like a heartbeat binary system. The primary appears to be another hot F or A-type star (~F5V in this case) as we have seen in other examples. Also nearby 220539859 does not have these features.
  

  s1=2571.45 p1=19.6 d1=1.1 (26.4 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220540678 , 2MASS J01174355+0740562 , 9.235 , 9.043 , 8.991 , 0.192 , 0.052 , ('F5V', 1.32) , ('F3V',1.43)
  
  220540626 , 2MASS J01174374+0740527 , 11.778 , 11.343 , 11.171 , 0.435 , 0.172 , ('K3V', 0.81) , ('K7V',0.64)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220540678 19.4315 7.6823 0.0 10.119 8
  
  220540626 19.4323 7.6813 4.49 13.281 8
  
  220539859 19.4505 7.6636 95.68 12.183 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220540678,2MASS J01174355+0740562,19.431488,7.682301,6515.00,1.58,1.33,10.119,-25.000,-7.000,235.4±80.24
  
  220540626,2MASS J01174374+0740527,19.432267,7.681320,5199.00,0.90,0.87,13.281,,,
  

  Listed as TYC 613-1179-1 -- Star on Simbad, Proper motions mas/yr: -13.20 -8.80, 01 17 43.5689 +07 40 56.294

  

  Posted July 26, 2016 2:56 PM

• by ajamyajax

  Re 220554210 from Hans Martin's list: looks like an interesting multiplanet candidate system of sub-Neptunes, with one possibly high impact. These fits use an estimate of 0.84 R_sol, but a blended look and the colors suggests longer durations and a higher stellar radius are possible. Also the nearby EPICs show a few transit-like features but these could be glitches and are different from this LC.
  

  s1=2562.0 p1=4.1698 d1=0.12875 (3.09 hours +/-)
  
  s2=2566.72 p2=27.245 d2=0.1645 (3.95 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220554210 , 2MASS J00534368+0759432 , 12.437 , 12.084 , 12.002 , 0.353 , 0.082 , ('G8V', 0.94) , ('G6V',0.97)
  

  Semi-Major Axis a (A.U.) = 0.169
  
  Stellar diameter ratio = 0.84
  
  Stellar mass ratio = 0.86
  
  Period ~= 27.267 days
  
  Duration ~= 3.9513 hours
  
  Estimated duration for center of star transit ~= 4.8351 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220554210 13.432 7.9953 0.0 13.723 8
  
  220554786 13.4231 8.0082 56.39 16.002 8
  
  220554613 13.3949 8.0044 136.16 12.827 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220554210,2MASS J00534368+0759432,13.432017,7.995316,5499.00,0.84,0.86,13.723,29.500,-6.600,440.3±42.48
  

  
  

  Posted July 26, 2016 2:58 PM

• by ajamyajax

  Re 220201207 from Ivan's list: seems to be a shallow or blended EB as indicated. Nearby 220201509 did not show these transits though.
  

  s1=2559.45 p1=0.437851 d1=0.065 (1.56 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220201207 , 2MASS J01143478+0002193 , 11.233 , 10.918 , 10.822 , 0.315 , 0.096 , ('G6V', 0.97) , ('K1V',0.86)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220201207 18.645 0.0387 0.0 12.350 8
  
  220201509 18.6484 0.05 42.29 13.023 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220201207,2MASS J01143478+0002193,18.644957,0.038747,5793.00,1.30,1.07,12.350,-5.300,-7.000,
  

  

  Posted July 27, 2016 2:08 AM

• by ajamyajax

  Re 220555384 from Han Martin's list: also could be a blended binary, but a chance for a high impact and near Earth-sized planet candidate when using a small star estimate of 0.44 R_sol. This seems to be a relatively nearby system with fairly high proper motions and a low distance estimate.
  

  s1=2560.484 p1=4.284789 d1=0.06833 (1.64 hours +/-)

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220555384 , 2MASS J00551490+0801220 , 10.494 , 9.827 , 9.700 , 0.667 , 0.127 , ('M7V', 0.098) , ('K4V',0.78)
  

  au min-max 0.04 0.04
  
  stellar diameter in solar units min-max 0.405 0.455
  
  stellar mass in solar units min-max 0.465 0.465
  
  period in days min-max 4.285 4.285
  
  duration in hours min-max 1.544 1.735
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220555384 13.8121 8.0228 0.0 12.395 8
  
  220556827 13.8307 8.0571 140.24 15.408 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220555384,2MASS J00551490+0801220,13.812051,8.022816,4145.00,0.51,0.57,12.395,24.300,-26.700,74.79±10.14
  

  

  Posted July 27, 2016 2:10 AM

• by ajamyajax

  Re 220615486 from Ivan's list: and identified as a CV by Ivan, this 19.058 KepMag target is listed on VSX and Simbad as a dwarf nova.
  Also the nearby EPICs do not show any sign of this outburst.
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220615486 19.0574 9.3711 0.0 19.058 8
  
  220616515 19.0637 9.3953 89.96 12.504 8
  
  220614182 19.0477 9.3395 118.97 15.768 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220615486,,19.057351,9.371101,,,,19.058,3.000,-6.000,
  

  From VSX:

  Dist. ' Name AUID Coords (J2000) Const. Var. type Period (d) Mag. range
  
  0.00 Variable CSS 081220:011614+092216 000-BJY-025 01 16 13.77 +09 22 16.1 Psc UG+E 0.06582 16.1 - 19 CV
  

  http://www.aavso.org/vsx/index.php?view=detail.top&oid=185507

  "UG: U Geminorum-type variables, quite often called dwarf novae. They are close binary systems consisting of a dwarf or subgiant K-M star that fills the volume of its inner Roche lobe and a white dwarf surrounded by an accretion disk. "

  Listed as CRTS CSS081220 J011614+092216 -- Dwarf Nova on Simbad, 01 16 13.764 +09 22 15.96

  

  Posted July 27, 2016 2:11 AM

• by ajamyajax

  Re 220466136 from Ivan's and Hans Martin's lists: this target could be another nice sub-Saturn planet candidate that seems to fit with a 0.68-0.74 R_sol star. Although a brown dwarf is another possibility (SF for your list). There are a few transit-looking overlaps in the nearby EPIC's but just one here and there per light curve that could be coincidental glitches.
  

  s1=2559.185 p1=17.106 d1=0.15 (3.6 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220466136 , 2MASS J01060501+0600305 , 14.039 , 13.472 , 13.433 , 0.567 , 0.039 , ('K6V', 0.7) , ('A5V',1.9)
  

  au min-max 0.125 0.125
  
  stellar diameter in solar units min-max 0.72 0.755
  
  stellar mass in solar units min-max 0.89 0.89
  
  period in days min-max 17.111 17.111
  
  duration in hours min-max 3.508 3.678
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220466136 16.5208 6.0085 0.0 15.540 8
  
  220464772 16.509 5.9817 105.33 13.514 8
  
  220464763 16.5051 5.9814 112.63 15.232 8
  
  220467420 16.5439 6.0335 122.19 16.218 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220466136,2MASS J01060501+0600305,16.520838,6.008470,4777.00,0.68,0.74,15.540,8.500,-3.300,
  

  

  Posted July 27, 2016 2:13 AM

• by ajamyajax in response to ajamyajax's comment.

  Update: just these 220466136's estimates over newer confirmed planets data that shows the "sub-Saturn desert" is still prevalent.. So perhaps the PC candidates in this range should be given a bit more stellar and BD scrutiny. 😃

  

  Posted July 27, 2016 2:30 PM

• by ajamyajax

  Re 220562610 from Hans Martin's list and Ivan's mention: another possible sub-Saturn planet candidate in a single transit event per Ivan's request. 1.4 R_sol estimate. This fit does look more planetary.
  

  s1=2563.687 p1~=99.671 d1=0.475 (11.4 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220562610 , 2MASS J01140698+0811157 , 11.370 , 11.107 , 11.041 , 0.263 , 0.066 , ('G0V', 1.09) , ('F9V',1.14)
  

  Semi-Major Axis a (A.U.) = 0.436
  
  Stellar diameter ratio = 1.4
  
  Stellar mass ratio = 1.11
  
  Period ~= 99.671 days
  
  Duration ~= 11.4013 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220562610 18.5291 8.1877 0.0 12.513 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220562610,2MASS J01140698+0811157,18.529059,8.187693,5915.00,1.40,1.11,12.513,-3.600,-11.900,
  

  

  Posted July 27, 2016 3:27 PM

• by Shellface in response to ajamyajax's comment.

  EPID 220204960: An unusual false positive, this lightcurve will take some effort to deconstruct. My thanks to aja for sharing the lightcurve with me.

  Though the star is not very faint (Kep = 12.7, V = 12.8), it does not have Huber et al. parameters. I find its reddened spectral type to be F9, but reddening towards the star seems to be significant. I estimate a real spectral type of ~F5, but the exact value is not too important.

  Edd has pointed out that there is a closeby star. This also appears in the SDSS, and I find the separation to be 3.4" **. I have recently come across a page detailing conversions from SDSS bands to Johnson-Cousins bands, which can be found here. From this and g-r = 1.57, I find a (reddened) spectral type for the star of M4-5. I estimate a magnitude difference in the visible of 4.3.This star seems to be too bright to be associated with the target for its spectral type (even when considering multiplicity), so I expect it lies in the foreground. Regardless, the presence of this nearby star is important to understanding the lightcurve.

  ** Edd, to estimate projected separations you must consider the centres of the stars, not the nearest points of their PSFs. Otherwise you will find considerable underestimates.

  The Kepler lightcurve shows an unusual set of transits, which can be seen in aja's plot. To the eye there appear to be two main sets with similar periods, which start close together then move apart until they reunite at the end. This is extremely unusual, and it took me some time to interpret them.

  Because it is difficult to associate the transits to a periodicity by-eye, I adopted an alternative approach. I calculated and tabulated all available transit times, then calculated the separations between successive transits. In the presence of a single periodicity one would find a constant transit separation, in the presence of two periodicities one would find two sets of transit separations, and in the presence of multiple periodicities and/or TTVs the diagram would be more complicated. The sort-of river diagram is shown below:

  

  Blue points are transit separations calculated from EXOFAST transit times, orange points involve transit times estimated by-eye due to malformations in their shape - presumably due to processing.

  It can be seen that the transit separations form two lines through time, which shows that the transits can be described as periodicities without TTVs. Additionally, there is some clear "choppiness" in the downward line, which is also present in the upper line (though it is not clearly visible on this scale). The chopping alternates on a per-transit basis in both cases, which indicate that the transits are actually due to double-period binaries with moderate eccentricities. This is perhaps not surprising, as every transit is perfectly V-shaped.

  The end result is that every second transit is associated with a certain periodicity, and only every fourth transit is actually due to the same object. Owing to the 0.6% transit depths both binaries must be severely blended ** to explain how the depths are all roughly the same, so none of the transits are actually associated with the target star.

  ** aja refers to blending a lot, but I have no idea what he means. It doesn't seem to be the standard definition, "combined light of multiple stars that causes decrease in apparent transit depth". To be clear, I always use that definition.

  EXOFAST is not suited to the modelling of blended transits, binary or not, so I do consider the fitted parameters useful. On the other hand the lightcurve plots are generally correct, so I show them below:

  

  

  Top are the plots for the ~13.27d transits and eclipses, bottom are the plots for the ~14.42d ones. While for the former pair the depth difference is fairly obvious for the latter both signals are equal within the scatter, so it is difficult to identify them as primary and secondary. I chose the one with the deeper depth in the model as the primary, but it is possible that the second is the primary.

  The four sets of ephemerides are:

  transit time (BJD - 2454833) + n * period (d)

  2568.8632 + 13.2691 * n (primary)

  2574.9903 + 13.2793 * n (secondary)

  2584.4319 + 14.4118 * n (primary?)

  2562.4938 + 14.4203 * n (secondary?)

  Interestingly, the differences in (apparent) period between primary and secondary seem to be significant. Attempting to fit a primary eclipse with the period of the secondary results in a very poor fit, and vice-versa. Since this cannot be physically true (this would break Kepler's laws, among other things) I suggest these are actually due to apparent TTVs caused by third bodies on wider orbits, possibly light travel-time effects or precession of periapsides. The magnitudes of the effects on both binaries are similar, so it may be that they are both due to each other, the two binaries forming a quadruple. In any case, the real periods of the binaries are likely intermediate between the those given above.

  It is possible to constrain how faint the binaries must be in order to produce such shallow transits/eclipses. The maximum transit depth of a binary with similar components is 50% (from a total eclipse), but it is likely to be somewhat lower. To explain the 0.6% observed depths the light of each binary must therefore be no fainter than (50/0.6) ≈ 80 times fainter than the target, in both cases. If the two binaries do form a quadruple then their combined light can be no fainter than ≈ 40 times fainter than the target. The brightness ratio between the target and the nearby M-dwarf is ~48 in the visible and it is likely to be somewhat lower in the Kepler band, so the transit/eclipse depths are compatible with being on the M-dwarf as a quadruple of near-equal components.

  If this is true, then this is a most unusual false positive - blended transits/eclipses from a double-eclipsing quadruple. The number of double-eclipsing multiple stars is very low, and the odds of one happening to blend with a brighter star is even lower.

  The combined light of M-dwarfs reaches merely V = 17 and it is near to a much brighter star, so follow-up of this system is unfortunately mostly infeasible. Still, this is an extraordinarily unlikely occurrence - very rarely are there lightcurves contaminated by two binaries, quadruple or not.

  Posted July 27, 2016 9:52 PM

• by zoo3hans

  Period of EB candidates (listed by DE or other hunters):

  EPIC 220712399 P=41.53 days

  EPIC 220666988 P=0.9285 days

  EPIC 220619415 P=16.0442 days, depth 0.04, U-shaped, could also be a PC in my opinion.

  EPIC 220614659 seems to be rather a pulsating variable

  EPIC 220231331 P=23.65 days

  EPIC 220220200 P=3.97 days

  EPIC 220204885 P=2.886 days

  EPIC 220592163 P=9.983 days

  EPIC 220588021 P=2.09775 days

  EPIC 220571578 P=10.619 days

  EPIC 220565349 P=21.778 days

  EPIC 220562140 P=0.3311 days

  EPIC 220551856 P=11.75 days

  EPIC 220551209 P=0.618 days

  EPIC 220550457 P=27.235 days

  EPIC 220544669 P=0.4034 days

  EPIC 220544503 P=28.92 days

  EPIC 220542353 P=15.247 days

  EPIC 220541275 P=16.718 days

  EPIC 220519942 P=1.041 days

  EPIC 220516443 P=0.7026 days

  EPIC 220514093 P=3.515 days

  EPIC 220513270 P=0.6512 days

  EPIC 220502355 P=11.04 days

  EPIC 220501719 P=0.861 days

  EPIC 220496837 P=8.899 days

  EPIC 220490873 P=12.044 days

  EPIC 220488981 P=2.296 days

  EPIC 220485301 P=0.9397 days

  EPIC 220479880 P=6.7894 days

  EPIC 220477223 P=9.369 days

  EPIC 220476633 P=3.041 days

  EPIC 220471927 P=19.88 days

  EPIC 220460233 P=1.433 days

  EPIC 220453029 P=30.27 days

  EPIC 220446493 P=0.23598 days

  EPIC 220443255 P=0.4549 days

  EPIC 220440299 P=4.4435 days

  EPIC 220434992 P=4.02 days

  EPIC 220431824 P=9.073 days, could be a PC

  EPIC 220429913 P=6.089 days

  EPIC 220414426 P=0.27456 days

  EPIC 220398184 P=2.696 days

  EPIC 220373025 P=0.2767 days

  EPIC 220370605 P=11.203 days

  EPIC 220352059 P=43.51 days

  EPIC 220351987 P=1.4779 days

  EPIC 220342646 P=0.4011 days

  EPIC 220339564 P=8.9807 days

  EPIC 220336320 P=1.7275 days (or double this value)

  EPIC 220320211 P=0.34255 days

  EPIC 220314572 P=11.03625 days

  EPIC 220314481 P=1.152 days

  EPIC 220314321 P=2.487 days

  EPIC 220305504 P=2.9865 days

  EPIC 220304223 P=3.2368 days

  EPIC 220230146 P=5.4554 days

  EPIC 220297500 P=1.479 days

  EPIC 220271452 P=0.874 days (looks contaminated though)

  EPIC 220258394 P=15.961 days (very eccentrical orbit)

  EPIC 220263105 P=0.7178 days (could also be a high impact PC)

  EPIC 220257938 P=6.4032 days

  EPIC 220243443 P=11.859 days

  EPIC 220228955 P=12.038 days

  EPIC 220222060 P=6.3657 days

  EPIC 220214860 P=0.7212 days

  EPIC 220219177 P=8.3606 days

  EPIC 220196587 P=11.3915 days

  EPIC 220187552 P=17.09 days (maybe PC, although V-shaped)

  EPIC 220173169 P=5.45 days

  EPIC 220162807 P=48.92 days

  EPIC 220170815 P=0.7584 days

  EPIC 220171401 P=0.2905 days

  EPIC 220179606 P=23.3525 days

  Posted July 28, 2016 7:10 PM

• by Shellface

  I'm not kidding when I say "no idea"! Something about transit shape?

  The lightcurve reductions have recently gone up on Vanderburg's website, so now I have no excuse for slacking.

  EPIC 220709978: This is one of the handful of K2 candidates brighter than V = 10, so it is a high priority target for investigation.

  Despite being bright for a K2 target (V = 9.5, Kep = 9.4) it is just faint enough to have avoided any previous study. Indeed, the star does not even have a Henry Draper designation. Thus there is nothing extra to work with, compared to a fainter star.

  The colours of the star indicate a (reddened) spectral type of G0 ± ~2 (5950 ± 200 K). Reddening in the direction of this star is moderate, but as it is quite nearby it is likely in front of most of it, hence I assume reddening is negligible (Huber et al. adopt E(B-V) = 0.025, which is indeed mostly negligible).

  There are no stars within 20" in the EPIC or in 2MASS. The SDSS image of the star is somewhat saturated, but there don't seem to be any nearby objects worth noting. As the star is itself bright any contaminator would have to be bright as well, so it seems reasonable to assume that there are no companions beyond ~2".

  Except for a few glitches, the out-of-transit lightcurve is very well-behaved, with only low-level variability. Aside from the usual systematic trend the variability is rotational, with a period of 27 days plus several harmonics. This is slightly longer than the solar rotational period, and rotational periods decay over time, so this indicates a close-to-solar age for the star. Additionally the semi-amplitude of the modulation is only 100 ppm; rotational amplitude scales with the proportional surface area occupied by spots and plages, so this very low amplitude indicates a low activity level for the star. At such a low activity level, I expect no major activity contribution to radial velocities, and very low activity in the classical activity indicators.

  In the recent HD 3167 paper it was noted that the lightcurve scatter increased by 80% after about Kepler date 2610. This is also observed in this star but at a lower ratio; moreover the difference is much stronger in HD 4628 (V = 5.7) and does not seem to be present in stars much fainter than this one, so it appears the scatter difference scales down with decreasing brightness. It should not greatly affect the study of fainter stars, and it is not too bad here either.

  I detrended the lightcurve as usual. Several of the transits were quite noisy, and I had to preen them of outlying points - this is probably due to a processing issue. With Teff = 5950 ± 200 K, the EXOFAST model is shown below:

  

  The stellar parameters agree well with the expected results, and the transit-derived density fits well, so the model generally supports a planetary interpretation of the signal.

  I find r/R = 0.02054 ± 0.00066 so for, say, R = 1.10 ± 0.05 Rsol then r = 2.47 ± 0.19 Rearth. This may be an underestimate if the star is more evolved, and it is also likely that the error on R will be larger (until Gaia results, perhaps), but this value of r should be a good working value.

  For the above radius, comparison with other planets indicates a probable mass of 6 - 10 Mearth, which corresponds to a radial velocity semi-amplitude of 1.5 - 2.5 m/s. Is this detectable? This is not a simple question to answer because there are several factors that go into RV planet detection, but to cover a few:

  • G-dwarfs are generally OK targets for RV observations in terms of spectral morphology, as they have well-characterised sets of lines. For a rotational period of 27 days the star should have a v sin i of no more than 2 km/s; though macroturbulence and microturbulence will contribute some broadening, generally speaking spectral broadening should not significantly affect the RV errors.
  • It has been established that this is a very inactive star, so there should not be much activity noise in the radial velocities. Activity is often a severe confounding element to RV studies, so the lack of it here is very fortunate.
  • Not many stars at V = 9.5 are intensively observed by spectrographs (though bright for modern transit searches, V = 9.5 is undoubtedly faint for spectroscopy), but the precision afforded is generally 1 - 1.5 m/s on HARPS, and slightly larger for HIRES. I am not very familiar with HARPS-N or the APF, but they should reach similar levels as HARPS and HIRES, respectively.

  Broadly speaking, then, this should be detectable. It will likely take considerable telescope time, but a 20% precision mass measurement is plausible.

  At a declination of +11.75 this is a target better suited for northerly spectrographs, but observations by the southerly examples is still possible to a lesser extent. Combined efforts of multiple spectrographs can significantly improve the viability of an observational campaign, and the combined efforts of the extremely precise HARPS and HARPS-N could very well make a detection in only a small number of observing seasons.

  This is towards the bright tail of Kepler detections, and it provides a small insight into the kind of systems that will be discovered by TESS. This is also one of the best small planets for mass measurement, and I hope such efforts will be successful.

  Posted July 29, 2016 11:20 PM

• by Dolorous_Edd

  EPIC 220709978

  UKIRT J-band

  1'x1'

  

  BTW there are also Y,H,K bands available, but which one is better to use? I know that these are different filters, wavelengths etc

  During K1 images used J filter

  Posted July 29, 2016 11:35 PM

• by Shellface

  BTW there are also Y,H,K bands available, but which one is better to use?

  i don't think it particularly matters if it's just for visual inspection. K is often used professionally for technical reasons (less contrast for redder objects), but to the eye the difference is not substantial.

  Posted July 29, 2016 11:57 PM

• by ajamyajax in response to Shellface's comment.

  Well every situation gets an objective look I hope, but to keep it simple I use possible blending to describe three transit observations with my usual quick analysis:

  1. the fitted transit depth is much less than it should be -- especially with V-shaped stellar looking transits and larger star systems, 2. the transit duration is much shorter than my Kepler's third law and my NASA borrowed calculation says it should be for the observed period. Of course with caveats often added for high impact and so forth. And 3. the light curve is either very messy or the transit events are uneven in non-star spot kind of ways. There is a good example of this just a page or two earlier, I think.

  Posted July 30, 2016 12:43 AM

• by ajamyajax

  Re 220321605 from Ivan's list and Hans Martin's mention: looks good as a mini gas giant planet candidate. The colors and the period/duration observed suggest a dwarf ~0.70 R_sol and a bit higher M_sol so that value used for this fit. But the star could be as small as 0.42 R_Sol per Huber/NEA. And nearby 220321122 does not show this transit. Also this system seems to be relatively nearby with high proper motions and a low distance estimate.
  

  s1=2566.64 p1=9.795 d1=0.12 (2.88 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220321605 , 2MASS J01134161+0305490 , 10.629 , 10.015 , 9.856 , 0.614 , 0.159 , ('K6V', 0.7) , ('K6V',0.7)
  

  au min-max 0.085 0.085
  
  stellar diameter in solar units min-max 0.685 0.725
  
  stellar mass in solar units min-max 0.855 0.855
  
  period in days min-max 9.789 9.789
  
  duration in hours min-max 2.808 2.972
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220321605 18.4234 3.0969 0.0 12.588 8
  
  220321122 18.4283 3.0866 41.08 13.318 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220321605,2MASS J01134161+0305490,18.423406,3.096936,4044.00,0.42,0.47,12.588,161.300,27.300,63.63±11.06
  

  Also listed as 2MASS J01134161+0305490 -- High proper-motion Star on Simbad, Proper motions mas/yr: 161 27, 01 13 41.62 +03 05 49.1

  

  Posted July 30, 2016 1:34 PM

• by ajamyajax

  Re 220588021 from Ivan's list: identified as a probable binary with a 2% drop and that does seem more likely. 1.28 R_sol would yield a transiting object ~19.6Re as shown though, so still a chance for a planet. But there could be a small secondary which doesn't help.
  Also there might be a similar transit at nearby 220586837 in the way of contamination, but it is faint. Nearby 220587734 looks clean however.
  

  s1=2560.944 p1=2.09764 d1=0.11 (2.64 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220588021 , 2MASS J00391430+0845561 , 12.417 , 12.178 , 12.081 , 0.239 , 0.097 , ('G0V', 1.09) , ('K1V',0.86)
  

  au min-max 0.03 0.035
  
  stellar diameter in solar units min-max 1.02 1.285
  
  stellar mass in solar units min-max 0.815 1.31
  
  period in days min-max 2.09 2.106
  
  duration in hours min-max 2.541 2.736
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220588021 9.8096 8.7656 0.0 13.419 8
  
  220586837 9.7969 8.7407 100.29 16.166 8
  
  220587734 9.7791 8.7598 110.48 13.389 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220588021,2MASS J00391430+0845561,9.809607,8.765594,6042.00,1.28,1.08,13.419,6.600,-9.400,732.2±179.4
  

  

  Posted July 30, 2016 1:36 PM

• by ajamyajax

  Re 220619415 from Ivan's list and Hans Martin's mention: this target has a neat U-shaped transit fit, but could be a little deep for a planet. The 1.23 R_sol Huber/NEA value calculates to a ~26.4Re transiting object. 0.84 R_sol gets this closer to around 18Re, but could be difficult to get both much smaller than that.
  

  s1=2564.476 p1=16.0442 d1=0.1854167 (4.45 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220619415 , 2MASS J01040114+0927439 , 12.046 , 11.760 , 11.670 , 0.286 , 0.09 , ('G1V', 1.07) , ('G9V',0.91)
  

  au min-max 0.11 0.135
  
  stellar diameter in solar units min-max 0.84 1.075
  
  stellar mass in solar units min-max 0.69 1.275
  
  period in days min-max 16.035 16.049
  
  duration in hours min-max 4.356 4.547
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220619415 16.0047 9.4622 0.0 13.133 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220619415,2MASS J01040114+0927439,16.004726,9.462200,5901.00,1.23,1.06,13.133,-0.600,-13.300,
  

  

  Posted July 30, 2016 11:54 PM

• by ajamyajax

  Re 220187552 from Ivan's, JKD's, and Hans Martin's lists: sparse transit data and fairly deep with a V-shaped fit, but with a 0.42 R_sol star a grazing gas giant planet candidate is at least possible. But two small dwarfs in a bound system seem a bit more likely here.
  

  s1=2566.315 p1=17.0933 d1=0.10 (2.4 hours +/-)

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220187552 , 2MASS J01195410-0029005 , 10.708 , 10.068 , 9.886 , 0.64 , 0.182 , ('M7V', 0.098) , ('K9V',0.6)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220187552 19.9755 -0.4835 0.0 12.836 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220187552,2MASS J01195410-0029005,19.975456,-0.483490,3882.00,0.43,0.48,12.836,9.700,-13.200,
  

  

  Posted July 30, 2016 11:55 PM

• by ajamyajax

  Re 220186645 from Hans Martin's list: nice spotting because a very shallow, possibly blended transit. And although these stellar estimates vary some, still a chance for a mini gas giant from 1.09 R_sol (shown with a mostly flat Astropy fit that I got as well) to a Neptune if a higher range estimate of ~1.44 R_sol. Also the nearby EPICs do not show any obvious sign of this transit. Of course contamination from a nearby binary is always possible (see below), but this fit is not obviously V-shaped which helps a bit.
  

  s1=2563.513 p1=7.0542 d1=0.1729167 (4.15 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220186645 , 2MASS J01093180-0031031 , 11.839 , 11.569 , 11.478 , 0.27 , 0.091 , ('G2V', 1.0) , ('K0V',0.89)
  

  au min-max 0.07 0.085
  
  stellar diameter in solar units min-max 1.13 1.44
  
  stellar mass in solar units min-max 0.92 1.65
  
  period in days min-max 7.047 7.061
  
  duration in hours min-max 4.052 4.249
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220186645 17.3825 -0.5176 0.0 12.961 8
  
  220186090 17.3881 -0.5395 81.43 11.006 8
  
  220186569 17.3584 -0.5204 87.31 18.800 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220186645,2MASS J01093180-0031031,17.382523,-0.517620,5991.00,1.09,0.97,12.961,-3.000,-30.300,
  

  

  Posted August 2, 2016 8:12 PM

• by ajamyajax

  Re 220222029 from Ivan's and Hans Martin's lists: another blended looking transit, but this target is contaminated from the primary transit of a nearby EB. That source is likely binary EPIC 220222060 (TYC 19-835-1 on Simbad) only 24.37 arcsecs away. It is also brighter and much closer based on the proper motions and distance estimates.
  

  s1=2561.746 p1=6.3656 d1=0.15 (3.6 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220222029 , 2MASS J01055295+0046377 , 13.429 , 13.050 , 12.949 , 0.379 , 0.101 , ('G9V', 0.91) , ('K3V',0.81)
  
  220222060 , 2MASS J01055456+0046420 , 10.730 , 10.431 , 10.334 , 0.299 , 0.097 , ('G4V', 0.99) , ('K1V', 0.86)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220222029 16.4707 0.7771 0.0 14.803 8
  
  220222060 16.4773 0.7783 24.37 11.925 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220222029,2MASS J01055295+0046377,16.470674,0.777143,5559.00,0.90,0.90,14.803,1.200,0.700,768.1±714.5
  
  220222060,2MASS J01055456+0046420,16.477342,0.778308,5855.00,1.05,0.96,11.925,-33.700,-37.600,273.2±95.01
  

  On Simbad n arcsecs away:
  
  24.30: TYC 19-835-1 -- Star on Simbad, Proper motions mas/yr: -33.7 -37.6, 01 05 54.562 +00 46 41.90
  
  155.14: WD 0103+005 -- White Dwarf, Proper motions mas/yr: 20 -77, Spectral type: DA, 01 06 02.971 +00 47 17.03
  
  170.40: SDSS-II SN 20663 -- SuperNova, 01 05 48.549 +00 49 14.54
  

  
  

  Posted August 2, 2016 8:14 PM

• by ajamyajax

  Re 220288191 from Ivan's and Hans Martin's lists: mentioned as a possible binary and does appear to be, or is contaminated by an EB. But another small dwarf, so a grazing gas giant still possible. There is also another event that might pass through a gap area. But nearby 220288388 and 220286997 both show either the same two transit events for P=29.29 or 2x this period, or they are just the same glitches in all three LCs.
  

  s1=2583.326 p1=24.4158 d1=0.0770833 (1.85 hours +/-)
  
  s2=2561.91 p2=29.29 d2=0.15 (3.60 hours +/-) <-(possible middle transit event in gap with this period)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220288191 , 2MASS J01325870+0223068 , 13.274 , 12.570 , 12.412 , 0.704 , 0.158 , ('M8V', 0.082) , ('K6V',0.7)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220288191 23.2446 2.3852 0.0 15.535 8
  
  220287996 23.2606 2.3808 59.84 11.573 8
  
  220288388 23.2074 2.3897 134.63 10.660 8
  
  220286997 23.2737 2.3604 137.57 15.770 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220288191,2MASS J01325870+0223068,23.244580,2.385196,3947.00,0.45,0.51,15.535,31.000,3.700,
  

  From Simbad 49.68 arcsecs away: CFBDS J013302+022312 -- Brown Dwarf (M<0.08solMass), 01 33 02.0 +02 23 12 (not visible in Aladin Lite, if coordinates are correct)
  

  

  Posted August 7, 2016 6:12 PM

• by ajamyajax

  Re 220487418 from Ivan's and Hans Martin's lists: seems to work ok as a sub-Neptune planet candidate. The Huber/NEA 1.36 R_sol value used for this fit. Also the two nearby EPICs do not show any sign of this transit. And the transit data for the range 2590.03925 to 2590.27675 BJD was removed because of glitches.
  

  s1=2562.014 p1=14.072 d1=0.2375 (5.7 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220487418 , 2MASS J00451161+0628536 , 11.009 , 10.747 , 10.679 , 0.262 , 0.068 , ('G0V', 1.09) , ('G0V',1.09)
  

  au min-max 0.115 0.14
  
  stellar diameter in solar units min-max 1.29 1.62
  
  stellar mass in solar units min-max 1.025 1.85
  
  period in days min-max 14.067 14.077
  
  duration in hours min-max 5.611 5.799
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220487418 11.2984 6.4816 0.0 12.062 8
  
  220486707 11.3065 6.4654 65.01 10.896 8
  
  220488673 11.3172 6.5095 120.9 13.387 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220487418,2MASS J00451161+0628536,11.298392,6.481562,6059.00,1.36,1.13,12.062,-1.800,4.800,
  

  

  Posted August 8, 2016 9:52 PM

• by ajamyajax

  Re 220712399 from Ivan's list and Hans Martin's mention, and SF you might want to take a look at this LC with its possible multi-eclipses...

  Maybe a slightly eccentric, small dwarf binary here with a possible third star for a trinary system, but other features could be anything. Also possible faint contamination in nearby 220711721 of some of these features. Edit: the possible eccentric binary transits are also shallow, so maybe those could be from another source.
  

  s1=2561.471 p1=41.53 d1=0.14 (3.36 hours +/-)
  
  s2=2581.45 p2=41.53 d2=0.10 (2.4 hours +/-)
  
  s3=2629.435 p3=? d3=0.18 (4.32 hours +/-)
  
  s4=2633.01 p4=? d4=0.07 (1.68 hours +/-) <- in Andrew's corrected data only...
  
  -and/or-
  
  s4=2591.25 p4=? d4=0.29 (6.96 hours +/-) <- in MAST corrected data only...
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220712399 , 2MASS J01044585+1149314 , 13.540 , 12.886 , 12.794 , 0.654 , 0.092 , ('M7V', 0.098) , ('K0V',0.89)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220712399 16.1911 11.8254 0.0 15.418 8
  
  220711721 16.1855 11.8062 71.92 18.005 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220712399,2MASS J01044585+1149314,16.191128,11.825434,4427.00,0.60,0.66,15.418,2.200,-1.800,
  

  

  Posted August 9, 2016 12:12 AM

• by Dolorous_Edd

  EPIC 220712399

  Also events at 2613.40 and 2633.02 glitches?

  UKIRT J-band 1'x1'

  

  Posted August 9, 2016 12:28 AM

• by JKD

  EPIC 220205657 - Signal at 2582.81 BKJD, Period =?; duration ~2.94 hrs, Depth ~9.3%

  Posted August 12, 2016 9:30 PM

• by JKD

  EPIC 220208795 likely an EB (already mentioned by DE on page 2 and JKD on page 4)

  Signal at 2572.94, BKJD, Period =?, Duration ~6.86 hrs, Depth ~22.6%

  Posted August 12, 2016 9:54 PM

• by ajamyajax in response to Artman40's comment.

  Re: "In the moment I'm typing this, Campaign 9 data is being downlinked."

  It's not there just yet. 2016 Sep 01 listed here for the scheduled data availability:

  http://keplerscience.arc.nasa.gov/k2-fields.html

  Posted August 22, 2016 5:26 PM

• by Artman40

  I know that. Also, will there be a delay when it comes to data release of campaign 9?

  Posted August 24, 2016 12:43 AM

• by ajamyajax in response to Artman40's comment.

  We'll see. I'll check once a day or so close to that time and hope you do also.

  Posted August 24, 2016 6:31 PM

• by ajamyajax

  And Campaign 9 includes the microlensing experiment:
  
  http://keplerscience.arc.nasa.gov/k2-c9.html

  Also the C9 data counts on ExoFOP-K2...

  Campaign 9 (standard) 623
  
  RA 18:01, Dec -21:46
  

  Campaign 9 (microlensing) 599
  
  RA 18:01, Dec -21:46
  

  Posted August 25, 2016 2:22 AM

• by ajamyajax

  30 Sep 2016
  
  K2 Campaign 9 data release (expected)

  From: http://keplerscience.arc.nasa.gov/

  Posted September 10, 2016 2:17 PM

• by zoo3hans

  Ok, so we need a bit of patience, it seems. Although I'm really interested to see this data, especially the microlensing events.

  Cheers, Hans Martin

  Posted September 10, 2016 5:37 PM

• by Artman40

  Question: about how massive objects could be detected with Kepler spacecraft?

  Posted September 11, 2016 1:38 PM

• by zoo3hans in response to Artman40's comment.

  I'd say unlimited. It routinely observes AGN's for example (Active Galatic Nuclei). It can observe anything which emits visible light, form asteroids to planets to stars to black holes to galaxies to whatever. What microlensing events can be detected I do have to inform myself in the coming weeks.

  Posted September 11, 2016 4:44 PM

• by zoo3hans

  EPIC 220383386 (HD 3167) now confirmed (again) with 2 planets in http://arxiv.org/pdf/1607.05248v2.pdf

  Posted September 16, 2016 7:44 AM

• by ajamyajax in response to zoo3hans's comment.

  C9 almost ready. 😃

  https://keplergo.arc.nasa.gov/k2-campaign-9-data-processing-complete.html

  Posted September 22, 2016 2:29 PM

• by Artman40

  C10 has also been downlinked. Raw data should be released very soon but as always, 2-3 months of delay until calibrated data.

  Posted September 23, 2016 5:09 AM

• by ajamyajax

  Re 220615486 from Ivan's list: indicated by Ivan as a possible CV and indeed this is considered a U Geminorum-type variable or dwarf nova.
  And I think a Kepler data animation helps confirm this is not a solar system crossing object with the brightening cycle of this dim 19.058 Kepmag target. There is a possible small asteroid crossing at 2608.4 though.

  s1=2607.2 p1=? d1=12.7 (304.8 hours +/-)

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220615486 19.0574 9.3711 0.0 19.058 8
  
  220616515 19.0637 9.3953 89.96 12.504 8
  
  220614182 19.0477 9.3395 118.97 15.768 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220615486,,19.057351,9.371101,,,,19.058,3.000,-6.000,
  

  From VSX:

  Dist. ' Name AUID Coords (J2000) Const. Var. type Period (d) Mag. range
  
  0.00 CSS 081220:011614+092216 000-BJY-025 01 16 13.77 +09 22 16.1 Psc UG+E 0.06582 16.1 - 19 CV
  

  https://www.aavso.org/vsx/index.php?view=detail.top&oid=185507

  Listed as CRTS CSS081220 J011614+092216 -- Dwarf Nova on Simbad

  
  

  Posted September 29, 2016 1:37 AM

• by ajamyajax

  Re 220469567 from Ivan's list: and for contrast another solar system planet crossing example, this object identified by Ivan in this thread as the planet Uranus. And the fairly similar midpoint with the DN just a coincidence I think, with the different animations as shown and very different locations per the RA/Decs.

  

  Posted September 29, 2016 2:15 AM

• by svaverbe

  All on this forum,

  I recently investigated the lightcurves for all stars with atmospheric parameters consistent with G spectral types in K2 campaign 8.
  The lightcurves from Vanderburg et al. were corrected for long term trends using Kipping's COFIAM algorithm. The lightcurves were then searched for transits using the BLS algorithm. A significant number of exoplanet candidates were found.
  Below is a list of the strongest detections. The columns include the EPIC id, the signal detection efficiency(SDE), the signal to noise ratio of the transits(SNR), the standard deviation of the lightcurve in mmag, the period P in days, the depth of the box fit signal in mmag, the duration of the box fit in minutes, the ratio q of the transit duration to the period and finally the Julian date of the first transit in the K2 lightcurve.
  I welcome any further comments and follow up on these objects and will occasionally post further updates.
  Is it possible to upload figures on this forum from other sources than websites ?

  • 220228500 12.968437 10.744481 0.365530 2.504696 1.447253 109.771038 0.030435 2562.475239
  • 220504338 11.935103 11.412962 0.967425 5.818013 5.901946 167.655954 0.020012 2565.721391
  • 220592745 11.690839 5.007599 0.108640 11.137098 0.330718 213.832275 0.013333 2571.602556
  • 220554210 11.587818 4.858476 0.327229 4.169272 0.677899 154.969246 0.025812 2562.016381
  • 220598367 11.437513 6.045370 0.707610 7.641755 2.835400 156.290493 0.014203 2563.721795
  • 220621788 11.284937 3.393443 0.092187 13.678019 0.256931 325.512274 0.016527 2568.294331
  • 220436208 11.202933 7.372861 0.291647 5.234506 0.972766 190.135951 0.025225 2563.529530

  Warmest regards,

  dr. Siegfried Vanaverbeke

  Posted November 7, 2016 7:38 PM

• by zoo3hans in response to svaverbe's comment.

  Dear Siegfried,

  please read our K2_C8 thread https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=2 , there you find for EPIC 220228500 comments from Ivan and Mark, who exstimated P=2.5044 days, duration 2.4 hours, radius 3.16 R_Earth.

  EPIC 220504338 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=4 , P=5.815 days, duration 2.66 hours, radius 8.53 R_Earth.

  EPIC 220592745 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=5 , wheree Ivan mentioned its period to be 11.134 days.

  EPIC 220554210 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=8 , where I and Mark note two planets, P1=4.1698 days, duration 3.09 hours, R1=2.62 R_Earth, P2=27.245 days, duration 3.95 hours, R2=2.24 R_Earth.

  EPIC 220598367 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6, where Ivan, Mark and I conclude that it may have one object with P1=7.6415 days and another with P2=5.274.

  EPIC 220621788 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=8, where Ivan, Mark and I have it with P=13.685 days, duration 3.67 hours, radius 1.91 R_Earth.

  EPIC 220436208 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6 , where Ivan reports it with a period of 5.236 days.

  Posted November 8, 2016 8:42 AM

• by svaverbe

  That is all pretty consistent. I have not yet modeled the transits in detail, this requires methods like MCMC to accurately characterize uncertainties on the diameter etc.. Durations from box fits are not very accurate. Some of the systems are indeed multiple, but the automatic search procedure does not search for multiples yet so it returns only the strongest box fit.

  Siegfried

  Posted November 8, 2016 5:05 PM

• by svaverbe in response to zoo3hans's comment.

  Some more detections from C8, still among G stars:

  • 220503236 11.194969 4.930943 0.147242 8.680556 0.471964 195.652174 0.015652 2563.480745
  • 220709978 10.866791 5.314585 0.066568 15.386983 0.244628 334.352077 0.015090 2566.088724
  • 220616148 10.550864 3.512539 0.261422 6.731740 0.401060 233.210894 0.024058 2565.549970
  • 220510874 10.277886 6.045214 0.152831 7.474959 0.479916 249.598627 0.023188 2562.927097
  • 220674823 10.109186 4.477236 0.174911 13.338669 0.464937 250.534997 0.013043 2572.774569
  • 220598410 9.220207 3.938834 0.540670 7.642339 1.563316 153.112592 0.013913 2563.722026
  • 220579319 8.122147 2.504040 0.180178 19.654088 0.236430 459.659414 0.016241 2564.142471
  • 220383386 7.747216 4.052874 0.130445 1.919496 0.256723 94.621646 0.034233 2561.376950
  • 220231017 7.622941 3.211357 0.151092 30.665440 0.113093 3188.921167 0.072216 2570.439433
  • 220186645 7.559591 2.466349 0.287107 7.054674 0.436557 264.933560 0.026079 2563.530519
  • 220631484 7.515022 2.550721 0.237357 13.260841 0.350552 287.817900 0.015072 2563.554378
  • 220471666 7.360585 2.494507 0.128332 8.269931 0.221826 196.752434 0.016522 2561.364880
  • 220644522 7.025398 2.350489 0.227847 13.663069 0.293291 279.358484 0.014199 2572.180058
  • 220487451 6.895414 2.371929 0.085621 26.546323 0.153169 542.772696 0.014199 2586.917402
  • 220616992 6.795132 2.080825 2.099227 3.295762 1.729485 114.209751 0.024065 2561.692046
  • 220638335 6.717344 2.621465 0.467460 19.208605 0.790892 425.050962 0.015367 2560.888019
  • 220594086 6.602092 2.968165 0.430034 23.126735 0.475440 1061.203576 0.031866 2580.244972
  • 220599459 6.574258 2.341189 2.686096 10.982976 2.945119 380.268058 0.024044 2560.881074
  • 220492447 6.426130 2.231455 0.058196 32.520325 0.044213 1481.680767 0.031640 2567.695218
  • 220506272 6.264128 1.940410 2.651294 11.547344 2.016103 357.179968 0.021480 2568.411163
  • 220161370 6.240731 2.185544 2.167221 12.914891 2.231761 377.448826 0.020296 2560.905108
  • 220526892 6.200259 2.124665 0.071776 29.239766 0.083917 671.437945 0.015947 2579.635924
  • 220647198 6.175478 1.965167 0.272082 13.269639 0.260444 293.717765 0.015371 2566.674439
  • 220222029 6.157820 2.973229 0.524827 6.366183 1.176045 127.508130 0.013909 2561.762481
  • 220409868 6.100047 1.914013 0.240707 9.256688 0.217394 193.239064 0.014497 2566.580747

  They are in order of decreasing signal detection efficiency, so the ones on the bottom of the list should be treated with some caution.

  Siegfried

  Posted November 12, 2016 9:32 AM

• by zoo3hans in response to svaverbe's comment.

  Dear Siegfried

  EPIC 220503236 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6 , where Ivan reports it with a period of 8.678 days.

  EPIC 220709978 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=9 , where Shellface report a period of 15.3878 days, radius 2.47 R_Earth.

  EPIC 220616148 not on our list

  EPIC 220510874 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6 , where Ivan reports it with a period of 7.473 days.

  EPIC 220674823 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=7 , where Ivan reports it with a period of 13.336 days.

  EPIC 220598410 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6, where Ivan and Mark classify it as an (blended) EB, period 7.6415 days.

  EPIC 220579319 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6 , where Ivan reports it with a period of 19.669 days.

  EPIC 220383386 (HD 3167) now confirmed (again) with 2 planets in http://arxiv.org/pdf/1607.05248v2.pdf , P1=0.96 days, P2=29.85 days.

  EPIC 220231017 not on our list

  EPIC 220186645 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=5 , where I report it with a period of 7.06 days.

  EPIC 220631484 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=7 , where Ivan reports it with a period of 13.266 days.

  EPIC 220471666 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=7 , where Ivan and Mark report it with a period of 8.27 days and a radius of 2.58 R_Earth.

  EPIC 220644522 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=7 , where Ivan and Mark report it with a period of 40.935 days (three times your period).

  EPIC 220487451 not on our list

  EPIC 220616992 not on our list

  EPIC 220638335 not on our list

  EPIC 220594086 not on our list

  EPIC 220599459 not on our list

  EPIC 220492447 not on our list

  EPIC 220506272 not on our list

  EPIC 220161370 not on our list

  EPIC 220526892 not on our list

  EPIC 220647198 not on our list

  EPIC 220222029 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=5 , where Ivan and I report it with a period of 25.438 days (four times your period) starting at BKJD 2568.14, and
  https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=10 , where Mark reports it with a period of 6.3656 days as an blended EB (from EPIC 220222060 (TYC 19-835-1 on Simbad)).

  EPIC 220409868 not on our list

  Posted November 12, 2016 9:06 PM

• by svaverbe in response to zoo3hans's comment.

  The BLS algorithm sometimes lands at an alias of the true period, so I am not surprised it happens with EPIC 220222029. This needs a check. Interestingly, some objects are found which are not in the previous lists.

  Siegfried

  Posted November 13, 2016 9:36 AM

• by zoo3hans in response to svaverbe's comment.

  EPIC 220616148 discovered by Siegried seems to have 2 planets:

  P1=6.73174 days, starting at BKJD 2565.5, duration about 5-6 hours, depth 0.0006

  P2=15.155 days (as stated by Mark), starting at BKJD 2574.78, duration about 6-7 hours, depth 0.0007

  Posted November 13, 2016 12:22 PM

• by Dolorous_Edd

  Re: 220616148

  UKIRT 1'x1' J-band

  

  Posted November 13, 2016 4:20 PM

• by zoo3hans in response to Dolorous_Edd's comment.

  Skyview of EPIC 220616148 seems to look OK. Thanks Ivan.

  Posted November 13, 2016 7:09 PM

• by ajamyajax

  Re 220616148 from Siegfried's list and research plus Hans Martin's and Ivan's closer look: nice find and agree sure looks convincing as a multi-planet candidate in both Andrew's and Everest corrected data.
  

  s1=2565.535 p1=6.73 d1=0.16 (3.84 hours +/-)
  
  s2=2559.627 p2=15.16 d2=0.21 (5.04 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220616148 , 2MASS J00570055+0923097 , 12.553 , 12.259 , 12.217 , 0.294 , 0.042 , ('G2V', 1.0) , ('A7V',1.76)
  

  Semi-Major Axis a (A.U.) = 0.07
  
  Stellar diameter ratio = 1.12
  
  Stellar mass ratio = 1.004
  
  Period ~= 6.737 days
  
  Duration ~= 3.8418 hours
  

  Semi-Major Axis a (A.U.) = 0.12
  
  Stellar diameter ratio = 1.12
  
  Stellar mass ratio = 1.004
  
  Period ~= 15.153 days
  
  Duration ~= 5.0337 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220616148 14.2523 9.386 0.0 13.670 8
  
  220616883 14.2189 9.4036 134.59 12.574 8
  
  220617082 14.2214 9.4086 136.62 13.599 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220616148,2MASS J00570055+0923097,14.252307,9.386048,5912.00,1.12,0.99,13.670,9.400,-8.500, 659.4±249.2
  

  Summary of K2 Program GO8077
  
  "Title: The Masses and Prevalence of Small Planets with K2 - Cycle 3"

  https://keplerscience.arc.nasa.gov/data/k2-programs/GO8077.txt

  
  
  

  Posted November 14, 2016 12:08 AM

• by Dolorous_Edd

  EPIC 220579319

  Looking at EVEREST data

  period could be 39.321

  2 clearly visible transits, at 2583.74 and 2623.06

  EPIC 220592745 - MPC?

  Possible second PC ; dips at 2572.07, 2578.76, 2592.09, 2605.42, 2618.7904, 2632.11

  EPIC 220598367

  period 5.276 starting from 2562.39? unralated dips at 2563.686, 2563.686, 2617.19 , 2632.47 ?

  EPIC 220621788

  Maybe second PC? at 2580.84

  EPIC 220674823 - published MPC https://arxiv.org/abs/1611.00397

  Posted November 14, 2016 6:53 AM

• by zoo3hans in response to Dolorous_Edd's comment.

  EPIC 220579319 looks indeed more like the doubled period, i.e P=39.34 days.

  Posted November 14, 2016 7:09 PM

• by svaverbe

  And a number of additional candidates among K stars in the C8 sample:

  • 220555384 14.645643 4.708832 0.104597 4.285041 0.239581 98.341130 0.015937 2564.773873
  • 220321605 12.097908 5.443739 0.170191 9.797198 0.811040 200.373997 0.014203 2566.679488
  • 220220200 11.899227 11.752498 4.029595 1.984481 17.573227 90.311451 0.031603 2560.737457
  • 220400100 11.479938 4.456865 0.281748 10.795639 0.681845 234.380231 0.015077 2569.447201
  • 220650843 10.300824 3.672364 0.389503 10.228086 0.744991 234.733247 0.015937 2561.725987
  • 220303659 9.062165 6.009058 1.572354 2.047963 3.807254 70.948572 0.024058 2561.470948
  • 220629489 7.404635 4.109558 0.478636 1.921045 1.438192 96.993013 0.035062 2561.913318

  Siegfried

  Posted November 14, 2016 7:11 PM

• by zoo3hans in response to Dolorous_Edd's comment.

  EPIC 220592745 looks indeed like a multiplanet system.

  P1=11.143 days, starting at BKJD 2560.45, duration 7.5 hours, depth 0.0005

  P2=6.665 days, starting at BKJD 2565.42, duration 6 hours, depth 0.00015

  Posted November 14, 2016 7:23 PM

• by zoo3hans in response to svaverbe's comment.

  The following EPIC's look NOT convincing visually:

  220487451

  220231017

  220409868

  220492447

  220506272

  220526892

  220594086

  220616992

  220638335

  220647198

  Posted November 14, 2016 7:29 PM

• by Dolorous_Edd

  EPIC 220303659

  Nothing interesting in EVERST, but multiple dips in Andrew's data

  https://www.cfa.harvard.edu/~avanderb/k2c8/ep220303659.html

  There is a star nearby , so perhaps contamination

  Posted November 14, 2016 9:38 PM

• by zoo3hans in response to svaverbe's comment.

  EPIC 220220200 not on our list

  EPIC 220303659 not on our list, but see Ivan's comment above

  EPIC 220321605 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=10 , where Mark, Ivan and I conclude it's a sub-Neptune planet candidate with P=7.795 days and R=2.96 R_Earth

  EPIC 220400100 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=6 , where Ivan reports it with a period of 10.795 days.

  EPIC 220555384 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=9 , where Mark and I report it with a period of 4.284789 days and radius 0.98 R_Earth.

  EPIC 220629489 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=5 , where Mark and Ivan report it with a period of 1.9206 days, although Mark considers it to be stellar.

  EPIC 220650843 https://talk.planethunters.org/#/boards/BPH0000007/discussions/DPH0001fyy?page=7 , where Ivan reports it with a period of 10.224 days.

  Posted November 15, 2016 9:39 AM

• by zoo3hans in response to Dolorous_Edd's comment.

  Using AKO I get a period of 0.6826543 days instead of 2.047963 days (slightly detrend LC) for EPIC 220303659 :

  P=2.047963 days

  

  P=0.6826543 days

  

  Posted November 15, 2016 3:05 PM

• by ajamyajax

  Re 220592745 from Ivan's list and Siegfried's research and Hans Martin's closer look: also an interesting possible MPC with maybe a blended-in super-Earth and a sub-Neptune planet candidate. Also covered in several c8 programs from proposals, so hopefully we'll see a mention of this system in a paper or two at some point.
  

  s1=2560.46 p1=11.135 d1=0.20 (4.8 hours +/-)
  
  s2=2565.42 p2=6.6705 d2=0.1683 (4.04 hours +/-)
  

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220592745 , 2MASS J00512286+0852034 , 10.849 , 10.509 , 10.424 , 0.34 , 0.085 , ('G6V', 0.97) , ('G8V',0.94)
  

  Semi-Major Axis a (A.U.) = 0.098
  
  Stellar diameter ratio = 1.18
  
  Stellar mass ratio = 0.995
  
  Period ~= 11.148 days
  
  Duration ~= 4.8019 hours
  

  Semi-Major Axis a (A.U.) = 0.069
  
  Stellar diameter ratio = 1.18
  
  Stellar mass ratio = 0.995
  
  Period ~= 6.68 days
  
  Duration ~= 4.0484 hours
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220592745 12.8453 8.8676 0.0 11.923 8
  
  220592291 12.8694 8.8574 93.31 15.505 8
  
  220592738 12.8851 8.8675 141.61 14.061 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist
  
  220592745,2MASS J00512286+0852034,12.845309,8.867640,5698.00,1.03,1.00,11.923,3.100,-24.700, 280.5±220.6
  

  Listed as TYC 605-518-1 -- Star on Simbad, Proper motions mas/yr: 3.1 -24.7, 00 51 22.874 +08 52 03.50

  Summary of K2 Program GO11032
  
  Title: Monitoring the Closest Stars in K2 Fields 11, 12 and 13
  
  https://keplerscience.arc.nasa.gov/data/k2-programs/GO11032.txt
  

  Summary of K2 Program GO8068
  
  Title: Characterizing Small Planets with K2 and HARPS-N
  
  https://keplerscience.arc.nasa.gov/data/k2-programs/GO8068.txt
  

  Summary of K2 Program GO8077
  
  Title: The Masses and Prevalence of Small Planets with K2 - Cycle 3
  
  https://keplerscience.arc.nasa.gov/data/k2-programs/GO8077.txt
  

  
  

  Posted November 16, 2016 1:48 AM

• by zoo3hans in response to ajamyajax's comment.

  EPIC 220504338 is now a confirmed planet. See https://arxiv.org/abs/1611.07614

  Posted November 24, 2016 8:40 AM

• by ajamyajax in response to zoo3hans's comment.

  "Astronomers discover a dense 'hot Jupiter' exoplanet orbiting a sun-like star"

  by Tomasz Nowakowski

  http://phys.org/news/2016-11-astronomers-dense-hot-jupiter-exoplanet.html

  Posted November 30, 2016 1:19 AM

• by zoo3hans in response to ajamyajax's comment.

  The asteroid crossing might be Maehata.

  Posted April 14, 2017 6:19 PM

• by ajamyajax in response to zoo3hans's comment.

  Yes, indeed! I even made this short animation back then but forgot to post it (always so much to do it seems):

  220615486, mid , Maehata , 9870 , MB>IMB , 18.9 ,http://vizier.u-strasbg.fr/cgi-bin/VizieR-5?-source=B/astorb/astorb&Name===Maehata, 0.017 , 44.132

  And this from K2ephem:

  Object 'Maehata' is visible in C8 (mag 18.1..19.2; 2.3..41.1"/h; ra 16.962..24.813; dec 8.287..11.734).

  

  Posted April 14, 2017 7:47 PM

• by ajamyajax

  Re 220221272 from your lists: ok making progress here, but this is time-consuming with the vespa runs and also trying to get reasonably close with the stellar dimensions. Basically the first three candidates look fine and pass the vespa tests, but the others are either more speculative with two transits, blended fits, or vespa false positives -- so far anyway. And the smaller dwarf params that Huber has on ExoFOP/K2 seem more consistent when compared with others in a short K1 survey I did of 750+ such m-dwarfs, including their JHK colors. I must admit though my own bias is to favor these tightly-packed objects all being rocky because if we increase the size of the host star, that would change.

  So that's my take so far, and on to the next candidate. And please consider all estimates to be just that, and they could change with additional information.

  s1=2559.60 p1=13.6267 d1=0.0748 (1.7925 hours +/-), 1.75Re +/- 0.1
  
  s2=2559.423 p2=6.68 d2=0.0589 (1.4131 hours +/-), 1.17Re +/- 0.07
  
  s3=2561.43 p3=4.1937 d3=0.0505 (1.2112 hours +/-), 0.84Re +/- 0.13
  

  Semi-Major Axis a (A.U.) = 0.07
  
  Radius (R_Sun) = 0.26
  
  Mass (M_Sun)= 0.25
  
  Period ~= 13.64533 days
  
  Duration ~= 1.7936 hours
  
  Duration in BKJD ~= 0.0747 days
  

  Luminosity in solar units 0.0135
  
  Radiation distance similar to Earth: 0.116 A.U.
  

  Conservative Range:
  
  Inner HZ limit (0.95 EAU): 0.11 A.U.
  
  Outer HZ limit (1.37 EAU): 0.159 A.U.
  

  Optimistic Range:
  
  Inner HZ limit (0.75 EAU): 0.087 A.U.
  
  Outer HZ limit (1.77 EAU): 0.205 A.U.
  

  Estimated planet radius 1.75 Re
  
  Insolation or stellar irradiation relative to Earth 2.716
  
  Estimated surface temperature 358 K, 84.53 C, 184.14 F
  

  ...

  Semi-Major Axis a (A.U.) = 0.044
  
  Radius (R_Sun) = 0.26
  
  Mass (M_Sun)= 0.25
  
  Period ~= 6.6734 days
  
  Duration ~= 1.4131 hours
  
  Duration in BKJD ~= 0.0589 days
  

  Estimated planet radius 1.17 Re
  
  Insolation or stellar irradiation relative to Earth 7.049
  
  Estimated surface temperature 454 K, 180.84 C, 357.48 F
  

  ...

  Semi-Major Axis a (A.U.) = 0.032
  
  Radius (R_Sun) = 0.26
  
  Mass (M_Sun)= 0.25
  
  Period ~= 4.20129 days
  
  Duration ~= 1.2112 hours
  
  Duration in BKJD ~= 0.0505 days
  

  Estimated planet radius 0.84 Re
  
  Insolation or stellar irradiation relative to Earth 13.064
  
  Estimated surface temperature 530 K, 256.55 C, 493.77 F
  

  ...

  EPIC, 2MASS, J mag, H mag, K mag, J - H, H - K, (J-H spectral type, stellar mass est) (H-K spectral type, stellar mass est)
  
  220221272 , 2MASS J01215987+0045044 , 12.118 , 11.545 , 11.294 , 0.573 , 0.251 , ('K6V', 0.7) , ('M2V',0.5)
  

  From NEA, K2 Targets within search area:
  
  EPIC Number RA [decimal degrees] Dec [decimal degrees] Distance [arc sec] Kepler-band [mag] Campaign Number
  
  220221272 20.4994 0.7512 0.0 14.256 8
  
  220221261 20.5209 0.7508 77.54 17.613 8
  
  220220988 20.4717 0.7405 106.95 13.203 8
  
  220221171 20.5339 0.7477 125.04 17.426 8
  
  220222021 20.5256 0.7765 131.2 17.312 8
  

  epic_number,tm_name,ra,dec,k2_teff,k2_rad,k2_mass,k2_kepmag,k2_pmra,k2_pmdec,k2_dist,k2_propid
  
  220221272,2MASS J01215987+0045044,20.499381,0.751209,3551.00,0.26,0.25,14.256,102.300,-61.500,72.64,GO8056_LC; GO8031_LC
  

  Programs:

  GO8056 Crossfield The K2 M Dwarf Program: Fields 8--10
  
  GO8031 Guzik Statistics of Variability in Main-Sequence Stars of Kepler 2 Fields 8 and 10
  

  NEA logg 5.02 feh -0.001
  

  NEA logg err1/2 0.07 -0.03
  
  NEA fe err 1/2 0.090 -0.210
  
  NEA teff err 1/2 105.00 -84.00
  
  NEA stellar E(B-V) Reddening 0.017
  

  Gaia pmRA 102.3
  
  Gaia e_pmRA 3.5
  
  Gaia pmDE -61.5
  
  Gaia e_pmDE 4.2
  

  Gaia Plx -- mas
  

  Gaia DR2 Plx 12.0702 mas
  
  Gaia DR2 distance in parsecs 82.85
  
  Gaia DR2 ePlx 0.1012
  

  Gaia DR2 PMRa 103.228
  
  Gaia DR2 ePMRa 0.144
  
  Gaia DR2 PMDec -59.601
  
  Gaia DR2 ePMDec 0.085
  

  Gaia DR2 RV -- km/s
  
  Gaia DR2 eRV --
  
  Gaia DR2 Teff 3859.78
  
  Gaia DR2 RSun --
  
  Gaia DR2 LSun --
  

  

  Posted May 29, 2018 11:02 PM

• by ProtoJeb21 in response to ajamyajax's comment.

  Great job so far. Do you happen to have those graphics made by VESPA (the ones with various probabilities of what a candidate signal could be) for all of the EPIC 220221272 candidates?

  Posted May 30, 2018 11:35 AM

• by ajamyajax in response to ProtoJeb21's comment.

  Yes, I save the vespa results data and the signal and fppsummary images for each period signal tested. With these preliminary tests though, I usually save the highest false positive probability of three runs, which is usually still a very low fpp if all goes well. Edit: Here is an example of a positive vespa results image.

  
  

  Posted May 30, 2018 2:47 PM

• by ProtoJeb21

  @ajamyajax my initial results on the possibility of other candidates around EPIC 220221272: based on three of my analyses and one analysis by Hans Martin on Exoplanet Explorers, there are four potential signals outside the orbit of the 13.6-day planet in need of further analysis.

  +s1: 20.748587 days, 0.0931 AU, transits at epochs 2568.201886, 2588.950473, and 2609.69906. Receives about 1.55 times as much sunlight as Earth with an equilibrium temperature of 285 K, placing it within the optimistic HZ if it exists.

  +s2: 31.79153 days, 0.1238 AU, transits at epochs 2589.726878 and 2621.518406. I found this one last month. Calculated to have a Teq of 247 K and 88% the stellar flux of Earth.

  +s3: 49.056768 days, 0.1653 AU, transits at epochs 2561.878218 and 2610.934886. A very dubious signal I posted to EE on September 2nd. Teq of 214 K and stellar flux 0.49x Earth’s.

  +s4: 25.71569 days, 0.1075 AU, first transit at epoch 2561.891013. Reported by Hans Martin on EE last month. Teq of 265 K and gets 1.16 times more sunlight than Earth.

  I will investigate those signals within the next few hours.

  Posted June 2, 2018 11:21 PM

• by ProtoJeb21

  Updates on the four potential signals:

  +s4 actually looks pretty decent. Despite having a low sigma value with LcViewer, adjusting its first transit epoch to 2561.827037 makes it look like a possible, albeit weak, planet candidate. It looks to be a relatively small planet, maybe 70-75% the radius of Earth.

  I have having doubts about +s2. It may just be noise, but I can't be entirely sure.

  +s1, the original EPIC 220221272.06, also looks pretty decent. In fact, it looks good enough for me to say that further analysis of the candidate should be done. Based on it's folded transit with LcViewer, it looks to be about three-quarters the radius of Earth, so it probably will be able to resist a runaway greenhouse effect despite its relatively high stellar flux. That is, of course, if it's a real planet. It's orbital period may also be slightly different than what I posted before.

  I can find no evidence in support of +s3.

  There are a few interesting potential transits I spotted, which occur at epochs 2608.340061 and 2605.346840. I'm unsure if there are any more.

  Posted June 3, 2018 2:12 AM

• by ajamyajax in response to ProtoJeb21's comment.

  Ok thanks. It will take some time to try and fit and then run thru vespa. And they could still be anything. The good news as you know, are the longer periods put those candidates in or near the HZ. But sparse data makes fits more speculative and even though they could be high-impact exoplanets with v-shaped transits, vespa uses a trapezoid curve fit and probably will classify those as fpp. I'll try though and we'll see what the results tell us.

  

  Posted June 3, 2018 2:38 PM

• by ajamyajax

  p.s. while we wait, I found a nifty new color index table for you to try. Seems newer and could be especially helpful where little other stellar data are available.

  http://www.pas.rochester.edu/~emamajek/EEM_dwarf_UBVIJHK_colors_Teff.txt

  Posted June 3, 2018 3:05 PM

• by ProtoJeb21 in response to ajamyajax's comment.

  That's pretty helpful. Using that color index, I found that EPIC 220221272's J-H value of 0.573 is comparable to that of an M5V to M4.5V dwarf, while its H-K value of 0.251 is comparable to that of an M3V dwarf. It looks like Huber's estimates for the star are almost spot-on, and maybe are slightly greater than in actuality. The color index, however, suggests a temperature between 3100 K and 3410 K, lower than both Huber's and Gaia's estimates.

  Posted June 3, 2018 3:32 PM

• by ProtoJeb21

  @ajamyajax I've been meaning to ask: what are the problems with EPIC 220221272.03 (the 2.23-day signal)? I know that VESPA found it more likely to be a false positive, but what about it made the algorithm pick that conclusion? Could the signal still be a planet given enough data processing? And do you have the VESPA results for it?

  Posted June 3, 2018 11:54 PM

• by ProtoJeb21

  An update on the color index analysis of EPIC 220221272: averaging out the J-H and H-K results, it looks like the star is an M4V main sequence dwarf with a temperature of about 3220 K and about 0.652% the luminosity of the Sun. If this is the case, then the outer four candidates (including +s1/C06, +s2/C07, and +s4/C08) are in the habitable zone, with the 9.729-day candidate getting about the same amount of sunlight as Venus.

  Posted June 4, 2018 1:07 AM

• by ajamyajax in response to ProtoJeb21's comment.

  Edit: p=2.232 more blended-in like others here, so just have to work more on those with Vespa. I think this a real signal though as you do. More later.

  Posted June 4, 2018 2:22 AM