2010 ET65


2010 ET65 (a.k.a. 471137) is a moving object from K2 campaign 101, 102. You can read more information about this object at the JPL Small-Body Database Browser here. Data was taken from 06 July 2016 to 20 September 2016.

2010 ET65 was proposed for by Kiss in GO10075. If you use this data, please cite their proposal. You can find the bibtex citation by clicking the button below.

@ARTICLE{asteriks,
               author = {{Hedges}, C. and Co},
                title = "{}",
              journal = {},
            archivePrefix = "arXiv",
               eprint = {},
             primaryClass = "",
             keywords = {},
                 year = ,
                month = ,
               volume = ,
                pages = {},
                  doi = {},
               adsurl = {},
            }
@MISC{2015ktwo.propGO10075,
	author = {{Kiss}, K. and {Szabo}, S. and {Molnar}, M. and {Pal}, P. and {Szabo}, S.},
	title = {Rotational properties of selected transneptunian objects in the Kepler K2 C8 & C10 campaigns},
	abstract = {The light curves of transneptunian objects (TNOs) hold informati
		on on the formation and evolution of the small bodies in the Sol
		ar System, as it is outlined in our White Paper, presented to th
		e GO Office in the early phase of the K2 mission. Our recent stu
		dy of the TNOs 2002 GV31 and 2007 JJ43 has shown (Pal et al., 20
		15) that the Kepler K2 mission can be very effectively used for 
		TNO light curve observations. Here we propose to study light cur
		ves of a selected set of TNOs in the K2 C8 and C10 campaigns wit
		h an optimised observing strategy. A part of our targets have av
		ailable thermal infrared data from Herschel Space Observatory me
		asurements (Müller et al., 2009), with accurate size and geometr
		ic albedo values. This is important in resolving the size and ab
		solute albedo ambiguity of the light cur e inversion techniques 
		(Kaasalainen et al. 2001). These methods are able to reconstruct
		 the shape and/or the surface albedo variegations based on the o
		bserved visual range light curve, however, the same shape and/or
		 relative albedo distribution can be produced by objects of diff
		erent size and median albedo combinations. With the synergy of H
		erschel and Kepler K2 light curve observations we will be able t
		o obtain a comprehensive picture of these objects. The other set
		 of objects in our proposed study are TNOs in mean motion resona
		nce with Neptune. Resonant objects are extremely valuable since 
		these objects were likely captured into these resonances during 
		the outward migration of Neptune. Physical characteristics of th
		ese objects can constrain evolutionary scenarios of the Solar Sy
		stem as different resonances swept up or captured objects from d
		ifferent initial locations. The rotational characteristics are o
		ne of these important constraints. The first trans-Neptunian obj
		ects in the K2 mission have been observed with long, thin pixel 
		mosaics covering the entire arc of the orbit around the stationa
		ry point. While this method undoubtedly provides the largest amo
		unt of data from a single target, it is not the most optimal in 
		terms of pixel budget per target. Targets farther from the stati
		onary points the exhibit quadratically increasing proper motions
		 leading to excessive pixel requirements. About 7000 pixels were
		 used in Campaign 2 to cover the path of 2007 JJ43, yet a small 
		gap around the stationary point meant that 21 days of data were 
		still lost. In contrast, 2002 GV31 was observable for 16 days du
		ring Campaign 1 with a single mask that contained only 500 pixel
		s. We propose to maximize the scientific return of the K2 TNO pr
		ogram by allocating smaller masks (1500-1800 pixels) for multipl
		e targets per campaign. The positive detection of 2002 GV31 indi
		cates that 20-30 day-long observations around the stationary poi
		nt may allow us to reliably determine the rotation periods and a
		mplitudes of targets as faint as 23 magnitudes. Pixel masks can 
		be further optimized if they are not centered on the stationary 
		point which is the westernmost point of their proper motion duri
		ng the observing run, but shifted slightly towards east (by 5-10
		 pixels).Proposed targets:Target name			  Brightness    Dynamica
		l class	  K2 cycle	Herschel obs.--------------------------------
		------------------------------------- (35671) 1998 SN165		V=21.5
			 	classical 			8		yes(135182) 2001 QT322		V=22.1	 	classical			
		8		yes(307616) 2003 QW90		V=22.0	 	classical,4:7		8		yes(308379)
		 2005 RS43		V=21.8	 	resonant, 1:2		8		yes----------------------
		------------------------------------------------             (26
		375) 1999 DE9	                V=21.2	 	resonant, 2:5 		10		yes(1
		27871) 2003 FC128		V=22.5		resonant, 4:5		10		no               2
		010 ET65	 	V=21.4		resonant, 1:3		10		no               2010 FC49
				V=22.1		resonant, 2:3		10		no---------------------------------
		------------------------------------}
	howpublished = {K2 Proposal},
	year = {2015},
	month = {June},
	url = {https://keplerscience.arc.nasa.gov/data/k2-programs/GO10075.txt},
	notes = {K2 Proposal GO10075}
}
                    Acknowledgement:
                    This work uses...

Download Light Curve

If only want the light curve of the object with the optimal aperture, download this product. This will give you one .fits file with several extensions. The first extension is the optimal apertures determined for this target. Further extensions contain a range of aperture sizes. You can read more in our readme.

Download Target Pixel File

Our code asteriks creates Moving Target Pixel Files, which are similar to Kepler/K2 TPFs, and contain stacks of images from the telescope. Moving TPFs track the motion of solar system objects, so that they are always centered in every image. Moving TPFs are background subtracted. The movie above shows a Moving TPF with background subtraction on the right.

Run our code

You can run our code asteriks to regenerate any of these light curves yourself, or generate light curves of other objects. You can read more about our code at our GitHub Page and you can read more about how the code works in our recent paper