LAST production releases - EranOfek/AstroPack GitHub Wiki

This page lists the AstroPack release tags that run in production on the LAST computers. For each tag it gives a short description and the changes since the previous tag (the "delta").

How the tags are used. A release is an annotated tag on main, named lv<major>.<minor>.<patch>. The LAST computers do not follow main: they are fixed at one tag. The tag is set in the LAST_tools file files/github-repos.gledmagicwater (branch:main,tag:<tag>), so last-fetch-from-github keeps them at the tag. A change reaches production only when a new tag is made and that file is updated. See issue #1266. Since lv1.0.8 a tag may instead sit on a maintenance branch (lv1.0.x, lv1.1.x, made from the previous tag), when main holds changes that are not ready for production.

What the numbers mean. The last number (lv1.0.1, lv1.0.2, …) counts fixes: each corrects a specific problem, and products made before and after it are otherwise made the same way. The middle number (lv1.0 → lv1.1) is a step of a higher level: it changes how the products themselves are made — the photometric calibration, the coadd algorithm, the product files — so products of different lv1.x series should not be mixed. lv1.1.0 and lv1.2.0 are such steps. All products made before each of them were removed from the archive, and all data are reprocessed with the new series (since 2026 Oct 22: lv1.2.0). The last number can also mark a change of a catalogue that the pipeline reads, with the same code (lv1.1.3: the forced-photometry list).

Database columns. The versions that added columns to the LAST database tables (image_visit, image_proc, src_visit, src_proc) or changed the meaning of existing columns are listed in LAST DB columns by pipeline version.

lv1.2 series (current)

Tag Commit Date In production Main changes
lv1.2.3 e4b10472f 2026 Nov 3 2026 Nov 3, last01e 05:40 UT (canary), the other 19 computers 20:01–20:09 UT; archimedes, WRX80, euler, newton, camilla, gauss between nights calibrators contaminated by neighbour light rejected: dense-field calibration scatter about 4× lower (#1454); bright-star halos measured against the local background (#1470); the reprocessing computers process 10-image visits
lv1.2.2 f41d51397 2026 Oct 29 2026 Oct 29, 14:36–15:45 UT, all 20 computers; archimedes, WRX80, euler, newton, camilla between nights a visit no longer fails when a sub-image's fitted stars lie in a narrow strip (#1460); a blank saturation level falls back to the default, so early-2022 PSF magnitudes are no longer all NaN (#1452)
lv1.2.1 44ba43e47 2026 Oct 25 2026 Oct 25, 09:40–10:08 UT, 18 computers (last04w, last08e down); archimedes and WRX80 between nights the background map is extended to the crop edges (no more flat edge zone); astrometry starts from the next epoch if the first is not solved (#1448); catalogue files over 2 GB saved (#1447)
lv1.2.0 89cd37099 2026 Oct 22 2026 Oct 22, 21:05 UT (checkout) and 21:10–21:12 UT (pipelines started), all 20 computers; archimedes New series. The PSF fit takes its background from the aperture ring, so faint PSF magnitudes are no longer too faint (#1442); background keywords and read noise in the background (#1441); astrometry asks the catalogue for at least the image's radius (#1300)

lv1.1 series (2026 Oct 19–22)

Tag Commit Date In production Main changes
lv1.1.3 0e31a57ef 2026 Oct 22 2026 Oct 22, 06:12 UT (catalogue) and 06:37 UT (tag), all 20 computers no code change: the forced-photometry catalogue ForcedPhotList updated, 85 fast radio bursts added
lv1.1.2 0e31a57ef 2026 Oct 20 2026 Oct 20, 18:01–18:55 UT, all 20 computers coadd photometric calibration: calibrator errors from Gaia alone, PT_NORM in m², new PT_FNORM (#1393, #1431); pipelineII PSFs without upside-down stars (#1355); a very bright star no longer rejects a whole visit (#1437); no more complex-number crash in pipelineII (#1360)
lv1.1.1 c8a4c4443 2026 Oct 20 2026 Oct 20, 12:01–12:08 UT, all 20 computers raw images with more than 2.3 times the expected pixel noise are rejected (was 4); astrometry uses at most the 3,000 brightest sources (#1400)
lv1.1.0 8e1799119 2026 Oct 19 2026 Oct 19, 10:39–10:41 UT, 19 computers (last08e later) New series. Photometric calibration no longer drops most calibrators of sharp crops (#1414); visit coadds made differently (#1355, #1166); epoch catalogues as two MAT files per visit (#1417); pipelineII galaxy matching works again (#1422)

lv1.0 series (2026 Oct 11–18)

Tag Commit Date In production Main changes
lv1.0.10 e6f9650b0 2026 Oct 18 2026 Oct 18, 15:53 UT, 19 computers (last04w off) bug fix: epoch images have LEVEL = proc, and their image IDs the "proc" level (#1412)
lv1.0.9 6b4ac367e 2026 Oct 18 2026 Oct 18, 14:21 UT, 19 computers (last04w off) bug fix: the background FITS writer keeps the image until the file is written; write failures are logged (#1391)
lv1.0.8 35c3e6ee5 2026 Oct 18 2026 Oct 18, 13:32 UT, 19 computers (last04w off) pipelineII reuses the demon's asteroid orbits (less memory); FITS files closed after an error (#1392)
lv1.0.7 ffcba2a5b 2026 Oct 17 2026 Oct 17, 19:37 UT, 19 computers (last04w off) the raw-image noise check measures 24 boxes across the image, not only the centre (LAST_issues #242)
lv1.0.6 f9c0e292a 2026 Oct 17 2026 Oct 17, 11:39 UT, 19 computers (last04w off) bug fix: forced-photometry flux errors include the source photon noise (#1408)
lv1.0.5 477959a8e 2026 Oct 16 2026 Oct 16, 22:45 UT, 19 computers (last04w off) hyperbolic orbits no longer fail the known-asteroid matching (#1410)
lv1.0.4 545f8492a 2026 Oct 15 2026 Oct 15, 19:40 UT, 19 computers (last04w off) pipelineI only for visits older than 2 days (reprocessing of archived data)
lv1.0.3 71cbf5380 2026 Oct 14 2026 Oct 14, 16:02 UT, all 20 computers much less memory on very dense fields: Gaia stars for the transient match read per sub-image (#1387)
lv1.0.2 26ba4efe0 2026 Oct 14 2026 Oct 14, 10:26 UT, all 20 computers correct barycentric JD and velocity in the transients database (#1395)
lv1.0.1 4ec180318 2026 Oct 13 2026 Oct 13, 19:35 UT, all 20 computers transients written to the database again (#1396); bright-sky images no longer rejected by the histogram check (#1179)
lv1.0.0 456c80f68 2026 Oct 11 2026 Oct 11, 18:10 UT (18 computers), last03w/last04w on Oct 13 first release

lv1.2.3

Commit e4b10472f on main, 2026 Nov 3 (lv1.2.2 + 27 commits). The products made with lv1.2.0–lv1.2.2 stay in the archive, and the reprocessing continues with lv1.2.3. Unlike the earlier lv1.2 fixes, this release changes the photometric calibration and the source catalogues, so products of lv1.2.3 and of the earlier lv1.2 tags are not made the same way (see "Differences from earlier lv1.2 products" below). Release note: #1266.

What changed in the pipeline.

  • Calibrators contaminated by neighbour light (#1454, Dana Kovaleva, 0a1a46e36, 9a1b17216): imProc.calib.fitPhotCalibTrans now rejects by default (AuditContamMax = 0.02) a calibrator with more than 2% of its aperture light from Gaia neighbours. The fraction is read from the FCONT column of GAIADR3spec (no Gaia cone search when the column is present); the catalogue copies on the LAST computers already have it.
  • Bright-star halos (#1470, e6510457a, 1cdcf19c2): imProc.sources.multiIterExtractor matches the bright-star halo step to the uniPSF stamp (MethodBS = 'unipsf', new default) and measures a star's wing at 10–12 pix above the local level at 40–50 pix (BS_FarAnnulusR, BS_TrigNoise = 'local'), instead of above twice the sky. In dense fields the light of unresolved neighbours had made nearly every star trigger a halo, and faint stars were lost. A catalogue with no sources no longer stops the extraction (#1469, 6416365ae).
  • WRobust coadd (#1404, f7729b382): imProc.stack.coadd_WRobust uses the scaled mean absolute deviation for the pixel scatter (StdMethod 3 → 2); the weighted MAD underestimated the scatter for few images and clipped good pixels.
  • 10-image visits on the reprocessing computers (e4b10472f): PipelineDemon in StaticRAWDir mode (used by the reprocessing computers) queued only groups of more than MinInGroup (10) images, while the LAST computers take 10. Whole nights observed in 10-image visits (for example early September 2023) were skipped; they are now processed.

The other commits change tools the pipeline does not run: reference-image building (coadd_Proper, combine_proper, stamp2full, buildRefImages), celestial.healpix, catalogue tools (gaiaFcont, addFcontGAIADR3spec, catsHTM.insertColumns), fast-motion fitting (#1459) and wiki figures.

Test before the tag (WRX80, 5 archive visits with lv1.2.2 and with lv1.2.3):

Field Calibration scatter PT_ARMS (mmag) Calibrators PT_NCALI Coadd sources
Normal (01.02.04, 2023 Dec 25) 5.7 → 4.5 125 → 117 −3.7%
Dense (01.08.03, 2023 Jun 15) 7.3 → 5.7 49 → 40 −5.0%
Blank saturation level (01.02.02, 2022 Sep 7) 15.5 → 9.8 12 → 9 −66%
Very dense, b ≈ 4° (01.02.03, 2022 Aug 16) 38.1 → 10.5 960 → 125 +10.4%
Sparse (01.02.03, 2022 Aug 18) 3.8 → 4.3 44 → 44 −13%

In the blank-saturation case the 26,000 lost sources have no Gaia counterpart at all; in the sparse field 97% of the lost sources have none; in the very dense field 97,000 sources are gained, 75% of them Gaia stars. A 10-image visit that lv1.2.2 skipped (01.08.03, 2023 Sep 4) is processed (calibration scatter 3.9 mmag). Run time and memory are unchanged. Canary night on last01e (2026 Nov 3): calibration scatter 4.1 → 3.7 and 4.3 → 3.5 mmag on its two cameras, while the lv1.2.2 cameras on the same mount were unchanged; no rejections or crashes.

Differences from earlier lv1.2 products.

  • Dense-field zero points move by about −0.05 mag (up to −0.11) when the contaminated calibrators are dropped, so dense fields reprocessed with lv1.2.0–lv1.2.2 and with lv1.2.3 differ by that much.
  • The source catalogues differ: mostly false detections removed, and in very dense fields real stars recovered; in one dense test field (01.08.03) about 2% fewer Gaia stars.

Deployment. Pinned in LAST_tools (e3587c8); on the computers only the pin line of the installed github-repos.gledmagicwater was changed, with no package rebuild. last01e was moved on 2026 Nov 3 at 05:40 UT as a canary for one night; the other 19 LAST computers followed between 20:01 and 20:09 UT, each pipeline stopped at the end of a visit, moved and restarted. The reprocessing computers (archimedes, WRX80, euler, newton, camilla, gauss) move between nights.

lv1.2.2

Commit f41d51397 on main, 2026 Oct 29 (lv1.2.1 + 34 commits). A fix in the lv1.2 series: the products made with lv1.2.0 and lv1.2.1 stay in the archive, and the reprocessing continues with lv1.2.2. Release note: #1266.

What changed in the pipeline.

  • Astrometry quality test (#1460, f41d51397): AstroWCS.populateSucess checks the residuals of a sub-image's fit on a 3×3 grid built from the area of the fitted stars. When those stars all lay in a strip narrower than one grid step, the grid was empty and the whole visit failed ("Operands to the || and && operators must be convertible to logical scalar values"). Now that sub-image is marked "astrometry not reliable" and the rest of the visit is processed. Seen on 3 visits, all on mount 06 west.
  • Saturation level (#1452, d13f5cbb0): imProc.mask.maskSaturated treats a saturation or non-linearity level that is not a positive number (a blank header card, read as 0) as missing and uses DefSatLevel/DefNonLinLevel. Before, every pixel was flagged saturated and the coadd photometric calibration found no calibrators, so all PSF magnitudes were NaN (a few early-2022 nights).
  • Calibrator audit (#1454, 0e6c42bf9): the photometric calibration can reject calibrators contaminated by Gaia neighbours in the aperture; off by default (AuditContamMax = NaN), so the products do not change.

The other commits change tools the pipeline does not run (database ingestion, ULTRASAT simulation, DESY analysis) or add functions it does not call (imProc.cat.coneTable).

Test before the tag (WRX80, the same 3 archive visits with lv1.2.1 and with lv1.2.2): a normal field (01.02.04, 2023 Dec 25) and a dense Milky Way field (01.08.03, 2023 Jun 15) are identical (all FITS data and headers except the creation dates, epoch catalogues, epoch headers and matched-source files). 01.02.02, 2022 Sep 7 (blank saturation level): PSF magnitudes NaN for all 36,955 coadd sources before, for none after; the images are unchanged. The 3 visits that failed on last06w (#1460) are processed normally.

Deployment. Pinned in LAST_tools (18299a5); on the computers only the pin line of the installed github-repos.gledmagicwater was changed, with no package rebuild. On the LAST computers each pipeline was stopped at the end of a visit, moved to lv1.2.2 and restarted (last01e at 14:36 UT, 17 more by 15:04 UT, last04w at 15:14 UT and last10e at 15:45 UT). The 2023 reprocessing computers (archimedes, WRX80, euler, newton, camilla) move between nights.

lv1.2.1

Commit 44ba43e47 on main, 2026 Oct 25 (lv1.2.0 + 18 commits). A fix in the lv1.2 series: the products made with lv1.2.0 stay in the archive, and the reprocessing continues with lv1.2.1. Release note: #1266.

What changed in the pipeline.

  • Background near the crop edges (b8e7a5d16): the background map is made of 512×512-pixel blocks. Between the outermost block centres and the image edges (about 320 pixels on a LAST crop) it was kept flat; now it is extended linearly (imUtil.image.sparse2full, option ExtrapMethod='linear', used by pipelineI for epochs and coadds). On a sloping sky the background there was off by up to about 1 ADU, which gave false or missed faint detections near the crop edges and a step of about 2 ADU between neighbouring crops.
  • Astrometry (#1448, 62670cef5): if the first epoch of a visit is not solved, the solution of the visit starts from the next epoch.
  • Large catalogue files (#1447, c3976c0f6): variables over 2 GB (epoch catalogues of very dense fields) are saved in the -v7.3 MAT format instead of failing.
  • Night report: the half-energy width (FWHE) in the night statistics.

The other commits since lv1.2.0 change ULTRASAT simulation code, not the LAST products.

Test before the tag (archimedes, 3 visits of 2022 and 2023, one in a dense Milky Way field, against the lv1.2.0 products of the same visits made on the same computer): no errors and the same product files. Inside the crops (more than 320 pixels from an edge) nothing changes: PSF magnitudes within 0.3 mmag, background unchanged. Within 100 pixels of the crop edges the background is higher by 0.02–1.05 ADU and there are up to 8 % fewer sources, almost all faint (S/N about 2) and without a Gaia DR3 counterpart.

Deployment. Pinned in LAST_tools (b0ab876, last-tool 1.0.9794.17133). On the LAST computers each pipeline was stopped at the end of a visit, moved to lv1.2.1 and restarted (last01e at 09:40 UT, the other 17 by 10:08 UT); the restart also reconnected the pipelines to the database, lost in the power cut of 2026 Oct 24. last04w and last08e, down since that power cut, are moved when they come back. archimedes and WRX80 (2023 reprocessing) move between nights.

lv1.2.0

Commit 89cd37099 on main, 2026 Oct 22 (lv1.1.3 + 39 commits). A new series: all products made with earlier releases were removed from the LAST computers, from archimedes and from euclid (/bigdata3, 18,404 visit folders, 21.9 TB), and all data are reprocessed with lv1.2.0. Release note: #1266.

What changed in the pipeline.

  • PSF photometry (#1442, ea187ee0d): the PSF fit in pipelineI takes the background of each source from the ring around its aperture, instead of the background map. Faint sources were measured too faint before.
  • Background (#1441, 19d1a51b9; f2e304d68): backVar with AddHeaderInfo=false no longer writes the background keywords (the source finder asks for them by default), and the read noise is no longer counted as a part of the background.
  • Astrometry (#1300, bd5c30702): for a catalogue given as input, the reference catalogue is queried over at least the radius of that catalogue.

The other commits since lv1.1.3 change ULTRASAT simulation, database-loading and tool code, not the LAST products.

Test before the tag (archimedes, 3 visits of 2022, 2023 and 2026, one in a dense Milky Way field, against lv1.1.3 on the same computer and input): no errors; PSF magnitudes brighter by 0.003–0.011 mag (median per visit, up to 0.05 in single sub-images); 3–12 % fewer catalogue sources. The sources that are no longer found are faint (S/N about 1.5) and only 8–31 % of them match a Gaia DR3 star, against 71–95 % for the sources found by both versions, so they are mostly noise peaks. FWHM, background, zero point and limiting magnitude are unchanged.

Deployment. Pipelines and product transfers were stopped on 2026 Oct 22 at 20:36–21:00 UT, the products were deleted, lv1.2.0 was checked out at 21:05 UT and pinned in LAST_tools (2773262, last-tool 1.0.9791.37969), and the pipelines were started at 21:10–21:12 UT. The visits of that night already processed with lv1.1.3 were processed again with lv1.2.0.

lv1.1.3

The same commit as lv1.1.2 (0e31a57ef on main), 2026 Oct 22. The code is unchanged; the tag marks a new version of the forced-photometry catalogue that pipelineI reads. Release note: #1266.

What changed. pipelineI measures, on every epoch, the flux at the positions of the catsHTM catalogue ForcedPhotList (white dwarfs from Gaia, AGN and cataclysmic variables from SIMBAD) that fall in the image (pipelineI, argument ForcedPhotCat). The copy of this catalogue on the LAST computers (/lastXXX/data/catsHTM/ForcedPhotList/, from 2026 June) was replaced by the version on euclid (/bigdata/projects/catsHTM/ForcedPhotList/, 2026 Sep 9):

  • 85 sources were added, with the source code origin = 7 and JD_Added 2026 Sep 8. They are positions of fast radio bursts (FRBs): of 9 checked in SIMBAD, 5 are within 0.5″ of a known FRB or its host galaxy (FRB 121102, 20181119D, 190714, 20220610A, 20221029A); the other 4 have no SIMBAD object within 5″. Their Epoch is the date of the burst (2012–2024); they have no magnitude and no proper motion. FRB 20240209A, which LAST observes often, is not among them.
  • The other 4,169,528 sources are unchanged. 49 of the 329 catalogue files and the index file ForcedPhotList_htm.hdf5 changed; the other 280 files are identical.

Effect on the products. Visits whose field contains one of the 85 positions get forced-photometry rows (FORCED = 1) at these positions in the epoch catalogues. Nothing else changes.

Deployment. The new files were copied to all 20 computers (and to last11e, which had no copy, and last11w) at 06:12 UT on 2026 Oct 22. Each computer's files were checked against euclid's checksum file list.euler.checksum._ForcedPhotList_, which is now also kept in the folder. The tag was fetched on the 20 computers at 06:37 UT. The pipelines were not restarted: PIPEVER is read from git at the start of each visit. About 220 visits started between 06:05 and 06:38 UT therefore have PIPEVER = ':lv1.1.2' although they may have used the new catalogue; this matters only for visits that contain one of the 85 positions. LAST_tools names lv1.1.3 since 31ad933 (last-tool 1.0.9791.12008).

lv1.1.2

Commit 0e31a57ef on main, 2026 Oct 20: everything on main up to this commit, so it also contains the two lv1.1.1 changes (which were made on the branch lv1.1.x). Release note: #1266.

Changes that affect the products

  • Photometric calibration of the coadds (PhotCalibTrans, by Dana Kovaleva; #1393, #1431): the spectral error of each calibration star now comes from Gaia alone, which changes the weights of the stars in the fit. PT_NORM is now an effective collecting area in m² (new keyword PT_NORMU = 'm2'), and the new keyword PT_FNORM gives the throughput, PT_NORM divided by the collecting area of a LAST telescope. In the test, the zero points moved by at most 0.008 mag and the coadd magnitudes by 0.001 mag (median). (648c69046, 55f40842b, 0057a3c94)
  • pipelineII: the PSFs that are rebuilt before the image subtraction leave out PSF stars whose cutout sums to zero or less; such stars entered the PSF upside down (#1355). In the test this changed 14 of the 56 difference images and the number of transient candidates by 0.03%. (7a99651bc)
  • pipelineI: the check of the background differences between the sub-images of an epoch uses the median of the background map instead of the image mean, so a very bright star in one sub-image (Rigel on 01.08.04, field 736) no longer rejects all the epochs of the visit (#1437). (8ec7627e1)

Changes that affect production processing only

  • pipelineII: the difference image and its PSF are computed with ifft2(..., 'symmetric'), so they can no longer come out complex and stop pipelineII (#1360, by Ruslan Konno). In the test the difference images were identical bit for bit. (effd57d02)
  • PipelineDemon: when pipelineII is skipped because the visit has no coadd images, the log says so, instead of "visit is NaN days old" (#1438). (750b4ed3d)
  • imProc.astrometry.astrometryCore: no header update when the input is a catalogue (#1440). (b9fd53094)

The other commits on main since lv1.1.0 do not touch the production processing: ULTRASAT and DESY laboratory tools, database ingestion tools, the night report, reference-image coaddition, help texts.

How it was tested. On last10w (its two pipelines stopped for the test), 3 archive visits were run through pipelineI and pipelineII with lv1.1.1 and with lv1.1.2:

Visit Coadd sources Coadd magnitudes, lv1.1.1 − lv1.1.2 (median / largest per sub-image) Transient candidates
01.10.03, 2026 Oct 14, field 1063 48,501, unchanged +0.0008 / 0.006 mag 78,694 → 78,667
01.10.04, 2026 Oct 14, field 1065 44,975, unchanged +0.0006 / 0.013 mag 17,685 → 17,683
01.10.04, 2026 Oct 7, field 732 30,573, unchanged +0.0013 / 0.003 mag 26,164 → 26,158

The coadd images and their PSFs are identical. Two runs of lv1.1.1 on the same visit gave identical products, and a run of lv1.1.2 without the buildPSF change gave difference images identical to lv1.1.1, so all the changes in pipelineII come from #1355. Run time (474–544 s) and memory (59–67 GB) are unchanged.

Deployment. last10w, the test computer, was moved first (17:59 UT on 2026 Oct 20); its first visit with lv1.1.2 finished without errors at 18:08 UT. The other 19 computers followed at 18:14–18:55 UT. Each pipeline was stopped at the end of its current visit, so no visit was cut off: a visit that had just been picked up stayed in new/ and was taken again after the restart. A first attempt on 15 computers gave up after 20 minutes and left them on lv1.1.1, because a busy pipeline starts its next visit within a second and the stop script missed that moment; the corrected script moved them at 18:42–18:55 UT. One visit of 01.02.04 (last02w) failed at 18:55 UT because its parallel pool did not start after the restart; the pipeline continued normally with the next visit. LAST_tools names lv1.1.2 since 18558bc (last-tool 1.0.9789.32305).

lv1.1.1

Commit c8a4c4443 on the new branch lv1.1.x, 2026 Oct 20: lv1.1.0 plus 2 commits (the same changes are on main as ee068f667 and 19ba03bf2). Nothing else from main is included. Release note: #1266.

Changes which raw images pipelineI accepts. Raw images with 2.3–4 times the expected pixel noise, which passed before, are now rejected. Products of accepted images are unchanged.

Changes that affect production processing

  • imProc.quality.noiseExcess (used by pipeline.generic.prePrep): default MaxRatio 4 → 2.3. Camera LAST.01.04.04 adds pixel noise that comes and goes; on 2026 Aug 10 its 1-s frames of 2023KY18 had 2.0–2.7 times the expected noise, passed the check, and gave 50,000–150,000 false sources per sub-image. Such a visit needed more than 125 GB of memory (issue #1400). (19ba03bf2)
  • imProc.astrometry.astrometryCore: new argument MaxAstSources (default 3000): at most this many of the brightest sources go into the pattern matching. It acts only when the first astrometry attempt fails and the second attempt uses all sources without filtering; before, the pattern matching then built tables of all pairs of sources and needed 150–240 GB on such frames (issue #1400). (ee068f667)

How it was tested. All 400 frames of the noisy 01.04.04 night: 394 are now rejected. The 91,734 frames processed on all cameras on 2026 Oct 17–19 have at most 1.6, so none of them would be rejected. On last10w, the noisy visit is now skipped in 1 minute at 8 GB (only 2 frames passed, too few for a visit); two normal visits (01.04.01 on the same dense field, 01.10.03 field 706) give the same 96 products as lv1.1.0, byte for byte, except the version keyword PIPEVER.

Deployment. last01e was moved first (12:01 UT on 2026 Oct 20), the other 19 computers at 12:06 UT. All 40 pipelines were idle (daytime) and restarted at 12:02–12:08 UT, with no errors. LAST_tools names lv1.1.1 since aaa9203 (last-tool 1.0.9789.21787).

lv1.1.0

A new series, one level above the ten lv1.0.x fixes. lv1.1.0 changes how the main products are made: the photometric calibration, the visit coadds and the files of the epoch catalogues. Products made with lv1.0.x and with lv1.1.0 are therefore not directly comparable. All products made before lv1.1.0 were deleted from euclid /bigdata3 and from the LAST computers on 2026 Oct 18–19, and the archived data are reprocessed with lv1.1.0.

Commit 8e1799119 on main, 2026 Oct 19. It contains everything on main since lv1.0.7, including the fixes of lv1.0.8–lv1.0.10 (made on the branch lv1.0.x). Release note: #1266.

What changes in the products

  • Photometric calibration (PhotCalibTrans, fitPhotCalibTrans): calibrator stars are no longer rejected for the CR_DeltaHT flag (#1414). Since #1331 that flag lands on nearly every bright star of a sharply focused crop, so such crops lost most of their calibrators and fell back to the reduced (zero-point only) calibration. In the test, reduced-mode crops went from 40 to 1 on 8 visits, and the affected crops have several times more calibrators (e.g. 3 → 47) and smaller residuals; the median zero point is unchanged (within 0.003 mag). (Dana)
  • Visit coadds (pipeline.generic.procCoadd, imProc.stack.coaddHeader): the epochs are brought to the same sky level before the outlier rejection, and the new keyword MAXBCKD gives the largest background difference of the coadded epochs (#1355); the coadd variance is scaled by the number of epochs per pixel (#1166). In the test the coadds have 1–6% fewer sources and a limiting magnitude about 0.01 mag shallower; magnitudes agree within about 0.001 mag, except where the sky changed between the epochs (one visit: 0.013 mag).
  • Epoch catalogues (pipelineI, imProc.io.saveProductMat): the 480 proc_Cat FITS files of a visit (20 epochs × 24 crops) are replaced by two MAT files, proc_Cat.mat and proc_Head.mat (#1417). The readers (queryDB.loadProducts/loadTable, the DB ingestion) read both forms. The visit gets faster to save and smaller. Approved by Eran and Chen.
  • Known asteroids are matched after the photometric calibration (#1423).

Fixes

  • pipelineII failed in the galaxy matching on every visit since lv1.0.5: catsHTM.cone_search selected more columns than the PGC catalogue files have (#1422, a regression of #1403).
  • All fixes of lv1.0.6–lv1.0.10 are included (#1408, LAST_issues #242, #1392, #1391, #1412); see their sections below.
  • Smaller: streak files store ORIGSEC/LIGHTSEC/CROPID (#1415); sliceGaussianProfile slice range clamped (#1389); maskSaturated (#1426), AstroImage.maskSet (#1427), astrometryRefine with catalogue input (#1055); pipelineII requests only the Gaia columns it uses (#1403).

Other changes (not used by the production pipeline)

  • DB ingestion and benchmark tools (pipeline.last.insertDB), Installer.installCatsHTM (#1425), nightReport, ds9_crops (#958), stellar-type helpers (astro.stars), ultrasat.simulateGaiaField.

How it was tested. 8 visits from 7 cameras, full pipeline (pipelineI and pipelineII), against lv1.0.10 and against the intermediate commits b762de0cf and b6dc3c4c1: a well-focused October night, a sharp April night, two N2 fields, the dense field 524, a soft-seeing camera, a moonlit visit, the field-841 visit of #1410, and a live visit of 2026 Oct 18/19. pipelineI succeeded on all; pipelineII on 7 of 8 (the 8th is the known #1405, as before). pipelineI is 3–7% slower; peak memory unchanged (59–65 GB). The final commit gives products identical to the tested candidate.

Deployment. 2026 Oct 19, with the pipelines stopped: all 20 computers moved to the tag; pipelines restarted at 10:39 UT (unit 1) and 10:41 UT (unit 2: simultaneous worker-pool starts can fail), last08e later; the first visits processed were those of the night of Oct 18/19. LAST_tools names lv1.1.0 since c9bc812 (last-tool 1.0.9788.19555).

lv1.0.10

Commit e6f9650b0 on the branch lv1.0.x, 2026 Oct 18: lv1.0.9 plus 1 commit (on main as 1c27e5850). Nothing else from main is included. Release note: #1266.

Products change only in three header values. In the epoch catalogs (proc_Cat, image header) LEVEL is proc instead of raw, and the level part of ID_PROC is "proc" (3) instead of "raw" (2); the coadd headers carry the corrected ID_PROC, ID_PROCF and ID_PROCL. ID_COADD, all other header values, all data and all file names are unchanged. Products made before lv1.0.10 keep LEVEL = raw; they are not corrected, because they will be reprocessed.

Changes that affect production processing

  • pipeline.last.pipes.pipelineI: sets LEVEL = proc in the epoch images before imProc.db.generateImageID makes ID_PROC (issue #1412). The v0 pipeline already did this in pipeline.generic.singleRaw2proc.

Tested on R2020b on a full visit with lv1.0.9 and lv1.0.10: 689 files, data byte-identical, only the values above differ; checked again on the first production visit on last01e.

Deployment. last01e was moved first (15:43 UT on 2026 Oct 18), the other 18 reachable computers at 15:53 UT, with the pipelines running; each restarted at the end of its current visit (only pipelineI changed, so no visit failed). last04w was off and is still on lv1.0.3; it needs lv1.0.10 with its pipelines stopped first. LAST_tools names lv1.0.10 since afcd171. The later last-tool 1.0.9787.29268 (LAST_tools 1d6f694) also makes the pipeline service wait for the data disks after a reboot: on 2026 Oct 18 a power cut rebooted six computers, and on last01e camera 01 MATLAB started before the disk with the star catalogs was mounted, so 8 visits failed until the next restart (their 160 raw images were moved back to new/).

lv1.0.9

Commit 6b4ac367e on the branch lv1.0.x, 2026 Oct 18: lv1.0.8 plus 1 commit (on main as 5ff75b590). Nothing else from main is included. Release note: #1266.

Products are unchanged (normal output files are byte-identical to lv1.0.8).

Changes that affect production processing

  • io.fits.writeThreadMexFITS, io.fits.DataKeeper, io.fits.mex.mex_fits_write_image_thread: the image handed to the background writer is kept until the writer reports that the file is written. Before, it was freed after 30 s even if writing was still going on, which could give a corrupt file or a crash on a slow disk (issue #1391). A write still running after 60 s is reported once in the service log. The writer now also reports failures (cannot open, short write such as a full disk, close error) with the file name; before, a write to a full disk counted as success. Messages go to stderr, because the AstroPack startup turns MATLAB warnings off. Only the Linux mex was rebuilt.

Tested on R2020b against the old writer: single/uint16/int32 files byte-identical; a write blocked for 70 s gave a completely wrong file with the old code (image freed at 30 s) and a correct file with the new one; failed open and /dev/full are reported.

Deployment. last01e was moved first (14:01 UT on 2026 Oct 18), the other 18 reachable computers at 14:15 UT, with the pipelines running; each restarted at the end of its current visit (all 38 by 14:21 UT). Because the fix changes a function and its caller together, a pipeline that was in the middle of a visit at the switch failed to save it ("Too many input arguments"): 3 visits (01.01.01, 01.03.02, 01.05.03), whose 60 raw images were moved back to new/. A release that changes a function and its caller together must be deployed with the pipelines stopped. last04w was off and is still on lv1.0.3. LAST_tools names lv1.0.9 since f3e8235 (last-tool 1.0.9787.25866).

lv1.0.8

Commit 35c3e6ee5 on the branch lv1.0.x, 2026 Oct 18: lv1.0.7 plus 2 commits (the same changes are on main as f935be42b and 8b1af1566). Nothing else from main is included; in particular the photometric-calibration change of #1414 is not in this release. Release note: #1266.

Products are unchanged.

Changes that affect production processing

  • pipeline.last.pipes.pipelineII: new argument OrbEl (default [] = load the 'merge' orbital elements as before); PipelineDemon now passes the set it loaded at start, so pipelineII no longer reloads ~1.5 million orbits every visit (about 0.4 GB and a few seconds per visit). Comets are still loaded in pipelineII (issue #1392). (63bbdabcd)
  • FITS.read1, FITS.writeTable1: the file is closed when an error happens between opening and closing it (before, each such error left one file open); writeTable1 also returns to the original folder. (35c3e6ee5)

Tested on R2020b with one local visit (field 1488) on lv1.0.7 and on lv1.0.8: all catalogs (epoch, coadd and subtraction, including the asteroid matches) byte-identical; other files differ only in write dates. Forced-error tests: no file left open (lv1.0.7: one per error). FITS.unitTest passes.

Deployment. last01e was moved first (13:16 UT on 2026 Oct 18), the other 18 reachable computers at 13:24 UT. Each pipeline restarted at the end of its current visit (all 38 between 13:17 and 13:32 UT). Daytime visits were reprocessing of old nights, so pipelineII was skipped (older than 2 days); of the first 80 visits 79 were processed and one failed because the parallel pool did not start (last02w, re-queued). last04w was off and is still on lv1.0.3. LAST_tools names lv1.0.8 since 63bf5d5 (last-tool 1.0.9787.24143).

lv1.0.7

Commit ffcba2a5b on main, 2026 Oct 17, 3 commits after lv1.0.6. Release note: #1266.

Changes which raw images pipelineI accepts. Noisy raw images that passed the pixel-noise check before are now rejected. Products of accepted images are unchanged.

Changes that affect production processing

  • imProc.quality.noiseExcess (used by pipeline.generic.prePrep): the ratio of measured to expected pixel-to-pixel noise is now the worst of a 4x6 grid of 500x500 boxes over the illuminated region (new arguments Nbox, default [4 6], and CCDSEC, default [1 6388 25 9600]), instead of one central box; MaxRatio unchanged (4). On LAST.01.06.03 in 2026 Jun-Sep the noise covered the whole sensor but was weakest at the centre, so about 1 in 5 noisy frames passed and gave visits with 35,000-45,000 false sources per sub-image (LAST_issues #242). The NoiseRatio value in the image table is now the worst-box value. (ffcba2a5b)

Changes not used by the production pipeline

  • astro.stars.tlogg2picklesClass: log(g) dwarf boundary as an argument, default 4.0 (was >4.5). (eafad117d)
  • New astro.stars.bprp2teff: Teff and log(g) from Gaia BP-RP, G and parallax (ULTRASAT). (f16b251da)

Tested on 4,319 set-aside 01.06.03 frames: 4,206 rejected (the old check: 3,386). Normal frames on 38 cameras (3,175, dense fields included) give at most 1.23. 0.25 s per frame. prePrep on whole visits: a normal 01.06.03 visit keeps all 20 frames; a noisy 01.05.02 visit is now rejected (worst box 5.1, centre 3.7).

Deployment. last01e was moved first (19:10 UT on 2026 Oct 17; pipelines restarted 19:10 and 19:13 UT); the other 18 reachable computers at 19:28 UT. Each pipeline restarted at the end of its current visit (all 38 between 19:10 and 19:37 UT); the first 29 visits had no failures. last04w was off and is still on lv1.0.3. LAST_tools names lv1.0.7 since 9284d7a (last-tool 1.0.9786.35087).

lv1.0.6

Commit f9c0e292a on main, 2026 Oct 17, 1 commit after lv1.0.5. Release note: #1266.

Bug fix that changes pipelineI products. The forced-photometry rows of the epoch catalogues had magnitude errors and S/N (MAGERR_PSF, SN; the catalogues do not store FLUXERR_PSF) without the source's own photon noise: too small for bright stars, by 1.5x at S/N 30-50, 2.4x at S/N 50-100 and 13x at S/N 200-400. All products made before lv1.0.6 (including the April 2026 reprocessing up to 2026 Oct 17) carry these errors in their forced-photometry rows. The regular PSF photometry of detected sources is not affected.

Changes that affect production processing

  • imProc.sources.forcedPhotNew (used by pipelineI) and imProc.sources.forcedPhot: default UseSourceNoise is 'last' (was 'off'); new Gain/KeyGain arguments, the gain is read from the image header (1 if missing) and passed to imUtil.sources.psfPhotCube. Forced-photometry fluxes change by about 0.1-0.3% (#1408). (f9c0e292a)
  • pipeline.last.phot.forcedPhot: default UseSourceNoise is 'last'. (f9c0e292a)

Tested on a 20-epoch visit (LAST.01.08.03, 2023 Jun 16, about 10,500 stars): the reported errors match the epoch-to-epoch scatter to within 5% up to S/N 50; an image copy in ADU with GAIN=2 gives the same fluxes and errors.

Deployment. last01e was moved first (10:50 UT on 2026 Oct 17); the other 18 reachable computers at 11:32 UT. Each pipeline restarted at the end of its current visit (all 38 between 10:53 and 11:39 UT); the first 33 visits had no failures. last04w was off and is still on lv1.0.3. LAST_tools names lv1.0.6 since b71dc1d (last-tool 1.0.9786.20772).

lv1.0.5

Commit 477959a8e on main, 2026 Oct 16, 5 commits after lv1.0.4. Release note: #1266.

Changes that affect production processing

  • celestial.Kepler.xyz2elements and celestial.OrbitalEl.nu2posOrbitalFrame: correct results for hyperbolic and parabolic orbits (they gave complex numbers and a reversed velocity). Elliptic orbits are unchanged. Before this, the one hyperbolic orbit in the catalogue (2024 UQ) made every visit near its predicted position fail in pipelineI (#1410). (477959a8e)
  • pipeline.last.pipes.PipelineDemon: new setting MaxOrbEccen (default 1); orbits with eccentricity of 1 or more are left out of the known-asteroid matching. (477959a8e)
  • pipeline.last.pipes.pipelineI: the known-asteroid matching runs per sub image; if it fails, that sub image is saved without known-asteroid matches and a warning is logged, instead of failing the visit. (477959a8e)
  • catsHTM.cone_search: trims each catalogue cell to the cone before joining them (less memory and time; same results); new options Method and Columns (#1403). (Dana, c44e499a2)

Tested on 01.09.03 (night 2026-04-05): the field-841 visit that failed in production succeeds; a normal visit with lv1.0.4 and with lv1.0.5 gives identical products (596 files) and the same list of matched known asteroids.

Other changes (not used by the production pipeline)

  • pipeline.last.reference.buildRefImages: no references from too few epochs (MinEpoch, #1404). (Dana, b719d0ded)
  • PhotCalibTrans: CCDSEC reports the header's section, never a fallback (#1393). (Dana, f1b6d4938)
  • nightReport: per-crop calibrator statistics. (Dana, 330e757eb)

Deployment. The 19 reachable computers were moved to the tag at 22:43 UT on 2026 Oct 16; each pipeline restarted at the end of its current visit. last04w was off and is still on lv1.0.3. LAST_tools names lv1.0.5 since e9581a3 (last-tool 1.0.9785.40920).

lv1.0.4

Commit 545f8492a on main, 2026 Oct 15, 7 commits after lv1.0.3 (plus 1 merge). Release note: #1266.

Changes that affect production processing

  • pipeline.last.pipes.PipelineDemon has a new setting PipelineIIMaxAgeDays (default Inf, no limit). A visit whose coadd MIDJD is older than this gets pipelineI only; pipelineII is skipped, the skip is logged ("Pipeline II skipped: visit is N days old"), and the products are still marked ready for transfer. startBatchLASTPipeline sets 2 days, so live visits keep pipelineII. Made for the reprocessing of archived raw images. (545f8492a)
  • imProc.stack.coadd_WRobust: the coadd header keyword COADDOP is wrobust (was the typo wrbosut). (1eabcabce)
  • tools.math.stat.rstd: a faster method for NaN-free vectors; results are identical (#1377). (Ruslan, 399e48b20)

Tested on 3 visits (01.01.02, 01.04.01, 01.07.01) with lv1.0.3 and the new code: the only difference is COADDOP in the coadd image and catalog files. A 36-day-old visit run with the 2-day limit skipped pipelineII, gave the same pipelineI products as the full run, and took 312 s instead of 370 s.

Other changes (not used by the production pipeline)

  • PhotCalibTrans / fitPhotCalibTrans: a selectable filter-curve store (FilterSource), and VO.ZTF reads a ZTF per-epoch catalog in the LAST format, for calibrating other missions (#1393). The default is unchanged. (Dana, 824a12347, 78e4f6726)
  • nightReport: a short summary of the night's problems, units on all plots, logarithmic histograms and a field check. (Dana, 41e1502c6)
  • imUtil.properCoadd.unitTest follows the properCoaddLinearR -> properCoaddLinear rename. (Dana, 883a98bc1)

Deployment. The 19 reachable computers were moved to the tag at 19:40 UT on 2026 Oct 15 and all 38 pipelines were restarted while idle. last04w was off and is still on lv1.0.3 until it is back. LAST_tools names lv1.0.4 since 39d1af6 (last-tool 1.0.9784.35482).

lv1.0.3

Commit 71cbf5380 on main, 2026 Oct 14, 4 commits after lv1.0.2 (plus 2 merges). Release note: #1266.

Changes that affect production processing

  • pipeline.last.pipes.pipelineII reads the Gaia stars for matching transient candidates for each sub-image (a cone of the sub-image half-diagonal + 300") instead of one catalog for the whole visit. Near the Galactic Centre the visit-wide query held 8.4 million stars and briefly needed about 20 GB more memory. Tested on 7 visits with lv1.0.2 and the new code: all products identical; peak memory 87.7 -> 63.5 GB (field 524) and 80.2 -> 63.5 GB (field 608); a normal field is not slower (#1387). (Ruslan, 0d7a36375)

Other changes (not used by the production pipeline)

  • imProc.stack.coadd_Proper: missing pixels are no longer counted as real measurements (#1399). (Dana, 3d85f884a); imUtil.properCoadd.properCoaddLinear updated. (Eran, 5398854eb) Production coadds use coadd_WRobust.
  • pipeline.last.reference.buildRefImages and imProc.stack.stitchCrops: reference building recovers the node number of old coadds and finds coadds named with a different time. (d5268dd84)

Deployment. The computers were moved to the tag at 16:01 UT on 2026 Oct 14 and each pipeline was restarted when idle (39 of 40 by 16:04 UT; 01.06.03 at the end of the visit it was processing). LAST_tools names lv1.0.3 since 607e04a (last-tool 1.0.9783.28891). The newer commit 399e48b20 (#1377) was not tested and is not in this release.

lv1.0.2

Commit 26ba4efe0 on main, 2026 Oct 14, 3 commits after lv1.0.1.

Changes that affect production processing

  • celestial.time.barycentricJD gave wrong results whenever it was called with more than one time or position: the light-travel-time correction and the barycentric velocity were divided by about the square root of the number of rows. imProc.db.insertCatalog calls it for a whole catalog at once, so the BJD and BARYVEL columns written to the database were wrong (in last.diff_src about 5 times too small). Single-value calls were always correct. Rows already in the database are not corrected by this release (#1395). (26ba4efe0)

Other changes (not used by the production pipeline)

  • pipeline.generic.procCoadd: a proper coadd is now always treated as background-subtracted by the source extractor (#1394). Production coadds use coadd_WRobust. (Dana, 3a79cd2bc)
  • imProc.calib.fitPhotCalibTrans: bands of other missions can be calibrated through a Mission setting (#1393). The default mission is LAST, and the LAST results do not change. (Dana, 394bcdf90)

Deployment. Deployed on 2026 Oct 14 with the pipelines stopped and restarted: last01e at 10:21 UT, the other 19 computers at 10:26 UT. LAST_tools names lv1.0.2 since 6338aa1 (last-tool 1.0.9783.18831).

lv1.0.1

Commit 4ec180318 on main, 2026 Oct 13, 24 commits after lv1.0.0 (plus 5 merges). Release note: #1266.

Changes that affect production processing

  • Transient candidates are written to the database again (#1396). Nothing had been written since 2026 Sep 18. Three code problems were fixed:
    • transient writing was not turned on in production;
    • the native ClickHouse connector failed on every insert (empty schema, numbers in the wrong column type);
    • NaN values made the insert fail. Re-reductions of visits older than 2 days do not write. (bbed03abf, 0670d4633)
  • The histogram check (imUtil.image.histAnomaly) is skipped when the sky is above 3000 ADU. On a bright (moonlit) sky it gave false alarms and rejected good images (#1179). (4ec180318)
  • imProc.sub.smearTemplate (used by pipelineII) uses the derived smear in preference to the measured one, and its S/N column is fixed. (Ruslan, 6da0e0ad2)

Other changes (not used by the production pipeline)

  • imProc.stack.coadd_Proper: the background is measured on the normalized coadd scale (#1329), and the PSF star count is set so the seeing is measured (#1390). Production coadds use coadd_WRobust. (Dana)
  • New ts.fitps functions (power-law and damped-random-walk power-spectrum fits) and ts.rand.randomPowerLawLightCurve. (Eran)
  • Database insert speed tests: imProc.db.insertCatalog gets a SkipDbInsert option (default false), plus a separate insertCatalog_perf, performance-logging functions, scripts and notes under pipeline.last.insertDB. (Chen)

Deployment. 0670d4633 (the #1396 fix) was deployed on 2026 Oct 13, 18:55 UT. 4ec180318 followed at 19:29–19:35 UT, and the tag was then made on that same commit. LAST_tools names lv1.0.1 since 6f46e44 (last-tool 1.0.9782.35472).

lv1.0.0

Commit 456c80f68 on main, 2026 Oct 11. This is the first release (#1266): the code that dev1 had when it was merged into main on 2026 Sep 26, with later fixes up to Oct 11. It runs the v1 pipeline (PipelineDemon) on all cameras. Its last changes before the tag:

  • the memory and file-handle leaks in the FITS writer, the FITS readers and sliceGaussianProfile are closed (#1388);
  • pipelineI frees the full-frame images after the cut into sub-images, about 9 GB less memory (#1367);
  • pipelineI runs maskHoles, fwhm and fitPhotCalibTrans on the parallel workers, about 25 s faster per visit (#1256).

There is no earlier tag to compare it with. For the changes made before Oct 11 see the New functions and changes log.

⚠️ **GitHub.com Fallback** ⚠️