Each observing session (date) consists of several FOV placements.
Each FOV set of images is processed independently of the others.
Therefore, there will be a LC for each FOV placement. This web page
is organized with the latest observing date at the top, and within
an observing date section LCs are arranged with time increasing
downward. The first graph for each date is the combined LC for all
LC segments that follow. Beneath each LC segment graph is a link to
the data upon which the graph is based. The header for that data
gives the FOV image center, number of reference stars used, number
of stars with APASS magnitudes used for setting the magnitude
scale, RMS of plot of APASS minus measured magnitudes versus
color (using a fitted slope of zero), etc. You may disregard the
sinusoidal fits to FOV data segments (these are used merely to
determine RMS scatter of the data with respect to a simple model).

data
Even though only 1 FOV placement was used for the night the
asteroid's movement was not in a straight line for a the entirety of
the observing session, so I'm treating the night's data in two
parts. Data gaps correspond to passage near background star.

Phase folded version of this observing session showing possible
eclipse, or transit, of the secondary.

Data
for Entire Observing Session Note the two vertical lines,
separated by 4.765 hours. No magnitude adjustments have
been applied to the FOV data segments.I spent ~10
days processing this observing session's data in the most
conscientious way I could devise (using a MFE, or mosaic-based
flattening equation, for flat field calibration), so I "believe in
it."See phase-folded plot (above) for explanation of a
difference in shape and level of the last FOV segment compared
with the first one.

Data
for Entire Observing Session MFE processed data. Note the
two vertical lines, separated by 4.764 hours. No
magnitude adjustments have been applied to the FOV data segments.
A fading trend is evident (even though each FOV segment has been
adjusted for ephemeris-predicted magnitude).

Data
for entire obs'g session. Combining FOV segments
(w/o mag adjustments).Both segments processed using MFE.
A secondary event is predicted for 4.0 UT, and it appears to be
present at 4.3 UT in this LC.