ARCKEEP v0.1 home engine how it works how to use uncertainty status

How to use ARCKEEP

A walk through one real measurement, from a folder of FITS frames to an ADES file for the Minor Planet Center. Each step shows the part of the engine you will use.

The pictures come from seven 19-second frames of the near-Earth asteroid 2019 FL1, taken at Tautenburg (site 033) on 29 March 2019. The frames are not part of the repository. Names in the ADES step are example values. To understand the method behind each step, read how ARCKEEP works.

ARCKEEP is a proof of concept built by first-year space technology students at LTU and coded with AI agents. Check what it tells you before relying on it.

  1. What you need
  2. Add your frames
  3. Let ARCKEEP solve them
  4. Look at a frame
  5. Check the frame's facts
  6. Compare candidate paths
  7. Review the track in Plot and Verify
  8. Identify the asteroid
  9. Resolve flagged frames and confirm
  10. Export ADES
  11. Workspaces and memory
  12. The terminal
  13. When something goes wrong

1 What you need

Your frames stay on your computer. ARCKEEP reads them in the browser and sends only sky positions and asteroid designations to its server (where your data goes).

2 Add your frames

Open the engine. Drag frames or a whole folder onto the drop area, or use Choose files or Choose folder. A folder becomes one sequence; loose files dropped together are treated as one sequence too. You can add several folders to the same workspace, and each stays a separate sequence.

The engine toolbar and the drop area with Choose files and Choose folder.
The toolbar and the drop area at the top of the engine.

A sequence of eight or more frames with round stars gets one question before anything is solved: Analyse the sequence before solving? Choose Analyse first (or type y) to have ARCKEEP line the frames up on their stars, set hot pixels and satellites apart, and look for one object moving in a straight line. Where that object is detected, it becomes the frame's target candidate, so you do not have to pick it frame by frame. The terminal reports what was found and how long it took, then solving starts. Choose Solve now (or type n) to skip it.

3 Let ARCKEEP solve them

Each frame is read, its stars found and matched to the Gaia catalogue. The file list shows each frame's status and, once solved, how many catalogue stars matched and the fit's RMS. A frame usually solves in a second or two, and the page stays usable while it works.

Seven solved frames in the file list, the first frame shown with its sources circled, and the terminal reporting each solve.
The whole engine after solving: files on the left with 38 to 43 catalogue matches each, the selected frame in the middle, the terminal below and the processing stages on the right.

The terminal logs every step: the pointing hint read from the header, the catalogue used, which centroids won, and the result. When every frame is solved it asks one question for the whole sequence, with buttons that say what they do.

The terminal ending with a highlighted prompt and two buttons: Review in Plot and Verify, and Confirm.
The sequence prompt. Review in Plot and Verify opens the review; Confirm accepts the track as it is. Typing n or y does the same.

The processing stages on the right describe the selected frame: Load, Solve, Target, Identify and Verify, and ADES. Each shows a result or a count rather than a bare word, and clicking stages 3 to 5 opens the view where their work happens. The ‹ button collapses the panel.

The Frame workflow panel: Load, Solve and Target complete, Identify and Verify next, ADES locked.
Stages for the selected frame. ADES stays locked until the sequence is confirmed in stage 4.

4 Look at a frame

Click any frame in the file list to show it. The Image view marks what ARCKEEP found. Each checkbox turns one kind of marking on or off and shows how many there are. Hiding a marking changes only the display.

Noise reduction smooths the displayed frame so faint objects stand out, which helps when you need to confirm that something is really there. It changes only what you see; every measurement still uses the original pixels. The same switch appears beside Export video in Plot and Verify: turn it on before exporting for a noise-reduced video, whose caption and file name then say so. Likewise Target marker there is the same switch as Target above: turn it off to see, or export, the frames without the red circle.

Zoom with + and - or the mouse wheel, drag to pan, and click the percentage to fit the frame again. Moving the pointer over the image shows the pixel position, its original value and, once solved, its RA and Dec. If ARCKEEP found no single candidate, or the wrong one, use Pick target and click the asteroid.

A frame with stellar trails circled in red and one round target candidate marked by a cross-hair.
The telescope followed the asteroid, so the stars are short trails and the asteroid is the one round source, marked with the cross-hair.

5 Check the frame's facts

The Info view lists the frame's facts: size, time, exposure, filter, instrument, the target candidate, and the time convention ARCKEEP applied. Check that row. It says whether the header time was taken as the start or the middle of the exposure, and whether that rule has been verified for your site.

If a header value is wrong or missing, correct it in Observation metadata and press Save metadata. Your values are local overrides: the FITS file is never changed, and Use FITS values restores the header. Changing the time or exposure re-runs the affected steps. The pointing and pixel scale cannot be edited here.

The Info view with frame properties and the observation metadata editor.
Frame facts, the Tautenburg time convention, and the metadata editor.

6 Compare candidate paths

Further down the Info view is the accepted fit: the catalogue, the frame's centre, scale, rotation and field, how many catalogue stars matched and the fit RMS. The fit RMS describes the star fit, not how precisely the asteroid is measured.

Below it, Compare paths draws known asteroids' predicted paths on the frame. The line under the form gives the time, position and radius to type into the MPC's MPChecker, which lists the known objects in your field. Paste up to 12 of its designations, check the site code, and press Compare paths. ARCKEEP says which paths cross the frame and draws them in the Image view.

The accepted fit table and the Compare paths form with 2019 FL1 entered and the result: 1 of 1 paths cross this frame.
2019 FL1's predicted path crosses the frame. A path tells you where to look; it does not identify the source by itself.
The frame with the predicted path of 2019 FL1 drawn through the target candidate.
Back in the Image view, the predicted path runs through the target. The MPC path count now shows its points.

7 Review the track in Plot and Verify

Open Plot and verify from the toolbar or the terminal prompt. The header summarises the track: number of frames, time span, the speed on the sky with its uncertainty, and how far the positions scatter about a straight line. A yellow box lists anything that needs your decision.

The top of Plot and Verify: track summary, a warning that one frame requires verification, and the known-object check.
The top of Plot and Verify: 47.77 arcsec per minute, scatter 0.148 and 0.090 arcsec, one frame to verify, and the identification result.

The plots show the same positions three ways: on the sky, against time, and as residuals from the straight line. A healthy track is a straight line of evenly spaced points with residuals of a fraction of an arcsecond. Play blinks through the frames with the target marked.

The sequence animation beside the sky-plane motion, position over time and fit residual plots.
Animation, sky-plane motion, position over time and residuals.

Below the plots, the cross-map table lists every frame: its time, file, RA, Dec and O-C, the distance from the line split into RA and Dec. View opens a frame. A flagged frame instead offers Confirm, if you agree with the track's choice, and Inspect.

The audit table: seven rows, six marked Consistent and the seventh flagged with 3 candidates, offering Confirm and Inspect.
The end of the table. Frame 7 is flagged: three sources could be the asteroid.

At the bottom, the sky context places your frame and the seven positions on a real sky map. Click a red position for its time, frame, coordinates and O-C; the slider fades the frame in and out.

An interactive sky map with the frame outlined and the seven red track positions on it.
The frame, outlined, on the sky map, with the asteroid's positions in red.

8 Identify the asteroid

When Plot and Verify opens, ARCKEEP searches every known near-Earth asteroid for one that matches the track. With one match it checks it at once; with several it lists them for you to choose; with none it says what was not searched. Frames more than 200 days from the date of the MPC's orbit file are out of reach, as these 2019 frames are. For them, find candidates with MPChecker and type the designation instead.

Type a designation in Object and press Check against orbit. ARCKEEP compares every position with the object's MPC orbit and answers in the box's title: Consistent with the object, time tags look off, or the orbit is too uncertain to judge. The text gives the mean offsets along and across the motion and the time offset they imply.

The known-object check reading Consistent with 2019 FL1, with mean O-C along and across the motion and a time offset of -0.2 plus or minus 0.1 seconds.
The seven positions agree with 2019 FL1's orbit at their time tags. A large, equal shift along the motion in every frame would point to a clock or time-convention error.

9 Resolve flagged frames and confirm

Inspect opens a flagged frame with what the track knows: its choice in a dashed circle, the other candidates numbered, and a cross where the track predicts the asteroid. Choose a candidate, pick a position yourself, or exclude the frame. Each choice returns you to Plot and Verify. To drop every flagged frame at once, use Exclude flagged frames in the yellow box that counts them; each excluded row keeps an Include button, and the track is refitted without them, which can flag a frame that passed before.

A flagged frame with candidates 1 to 3 circled, the track prediction marked with a cross, and buttons to use each candidate, pick manually, exclude the frame or go back.
Candidate 1, the track's choice, sits on the predicted position. Use candidate 1 confirms it.

Once no frame is flagged, the button in the header reads Confirm asteroid for 7 frames. One confirmation covers the whole sequence. You can also type y in the terminal. Changing a file, time, solve, target or the export scope afterwards cancels the confirmation.

The Plot and Verify header with the Confirm asteroid for 7 frames button enabled.
Every frame resolved: the sequence can be confirmed.

10 Export ADES

Confirming opens the ADES export for that one sequence. Fill in the object identifier (the designation or tracklet name you report under), the observation mode, the submitter, the measurers (one per line), the telescope design, aperture and detector. Observers, telescope name, focal ratio and filter are optional. An empty field takes the first frame's FITS header, such as APTDIA for the aperture or OBSERVER for the observers, and then what you last exported for the same station; a note under the field says which. Where you typed a value the header disagrees with, the note shows the header's value. ARCKEEP exports these exactly as they stand in the form.

Positions to export starts at five when more frames are confirmed, because the MPC asks for three to five positions of an object per night. ARCKEEP takes them evenly spaced across the sequence, so the first and last frames are always in. Empty the field to export every included frame.

The ADES 2022 PSV page: seven confirmed measurements ready, the submission context form and an empty export preview.
Seven confirmed measurements from station 033 are ready. The preview stays empty until the required context is filled.

Press Generate reviewed PSV. Read the file in the preview, then Copy PSV or Download .psv. ARCKEEP never sends it: you submit it to the MPC yourself, and the MPC decides whether to accept it. The per-position uncertainty fields are left out on purpose (why).

The generated ADES PSV file with header blocks for observatory, submitter, measurers, telescope and software, and one row per frame.
The generated file: one row per exported frame with time, RA, Dec, catalogue, exposure and fit evidence. A. Observer is an example name. The picture predates the optional fields and the five-position default.

11 Workspaces and memory

A workspace is a separate desk with its own files, selection, review and terminal history. + Workspace adds one, clicking a tab switches to it, and × closes it. Work continues in the background while you switch.

The toolbar with two workspace tabs, Workspace 1 with 7 files and an empty Workspace 2, each with a close button.
Two workspaces. The number in brackets is the file count.

ARCKEEP remembers your workspaces in this browser: the files, names, ADES details and every decision you made. Close the tab or come back tomorrow and they return as you left them: solved, with your confirmations. After an ARCKEEP update that changes how frames are solved, frames are solved again once; a confirmation stays unless the confirmed target has moved, and then ARCKEEP asks you to confirm it again. Only one tab saves; a second tab says so. They live only in this browser on this computer; another browser or a private window starts empty. Clear batch or removing a frame deletes it from the browser's storage too.

12 The terminal

Everything has a button, so the terminal is optional. Type help for the commands. They act only on the frames in this page; there is no access to your computer.

The terminal opened full size, listing the ARCKEEP commands after typing help.
The command list. Open in a panel's corner enlarges it; Restore puts it back.

13 When something goes wrong

You seeWhat it meansWhat to do
NEEDS HINT in the terminalThe header lacks the pointing or the pixel scale. ARCKEEP cannot solve a frame without them.Add RA, Dec and the scale (or a WCS) to the FITS header with your capture or processing software.
Solve refusedThe stars did not match the catalogue around the header's pointing, even after a second, wider attempt.Check that the header pointing is within a few arcminutes and that the frame shows stars. Very long exposures with long star trails can fail.
No target candidateNo single source has the opposite shape to the rest.Use Pick target, or let Plot and Verify choose from the track.
A flagged frameThe position is off the line, or several sources fit.Inspect it and choose, pick or exclude (step 9).
"Time tags look off"Every position is shifted along the motion by the same amount.Check whether your camera writes DATE-OBS at the start or the middle of the exposure, and correct the time in the Info view.
"Too far for the fast search"The frames are more than 200 days from the orbit file's date, or the object is not a near-Earth asteroid.Use MPChecker and Check against orbit.
A SERVICE line, or status in yellow or redAn outside service is slow or down: the star catalogue, the MPC, the sky viewer or the Gaia archive.Open the status page. Wait and retry; your frames are kept.
"Too many requests"The server allows a limited number of requests a minute per visitor.Wait a minute and try again.
The status page listing the star catalogue, Minor Planet Center, AstroEquip sky viewer and ESA Gaia Archive, all up.
The status page checks each outside service at most once a minute and says what each one affects.

Something else? Write to [email protected].