WFC3 UVIS Bowtie Monitor
The UVIS detector was observed during ground testing to occasionally exhibit flat field and dark variations with a bowtie pattern. These variations are most significant as ~1% flat field (gain) variations across the field of view. It is believed that this represents a state or condition into which the detector can transition for reasons
and under circumstances which are not currently understood. It is also very unlikely that most science observations will determine the state (bowtie or no-bowtie) of the detector. Ground test data indicates that this state is long lived (many hours to ~one day). Hysteresis or memory of past light exposure is also associated with this state.
Recent evidence suggests that exposing the detector to ~200k to 500k electrons may quench this state. This proposal obtains an internal flat field sequence of three exposures: one at 10x full well with two at 0.5x full well
immediately before and after. Each exposure is 3x3 binned to reduce the data volume required.
These visits should be scheduled 2x per day until further direction is provided.
Three internal (Tungsten) flats are obtained with the UVIS channel in the F475X filter. This filter was selected to provide high
throughput, limit the bandpass to wavelengths known to correct the bowtie effect (i.e. <700nm), and use a SOFA wheel with
relatively lower priority (hence lower usage frequence) filters.
Monitor and attempt to correct flat field non-uniformity.
Obtain exposures twice per day separated by at least 4 orbits. It is expected that the WFC3 team will provide direction during
SMOV to reduce the frequency of these flats.
12
false
0.0
0.0
false
false
false
false
false
RESTRICTED
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1
Execute approximately twice per day. There is no known benefit in running within 4 orbits of the prior iteration. Therefore, although
a AFTER requirement is not specified, it may be treated as after 5 to 10 orbits.
false
-1
-1