Pith. sign in

REVIEW 3 major objections 6 minor 29 references

SHINS, the SHARK-NIR Instrument Control Software

T0 review · 3 major / 6 minor · reviewed 2026-08-16 · deepseek-v4-flash

Pith's one-line read The paper claims that SHINS, the new instrument control software for SHARK-NIR at the Large Binocular Telescope, is a complete, web-operated control system that has already delivered early-science exoplanet detections and is ready for…

desk verdict Solid instrument-software description worth refereeing; just trim the readiness claim and fix the swapped INDI/SNMP sentence. read the letter →

arxiv 2504.19709 v1 pith:CTZFNVS4 submitted 2025-04-28 astro-ph.IM astro-ph.EP

classification astro-ph.IMastro-ph.EP
keywords SHARK-NIRSHINSinstrumentcontrolsoftwarecoronagraphicimagingobservationblocksRESTAPIICEmiddlewareTwiceAsNice
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

The paper presents SHINS, the control software for SHARK-NIR, a near-infrared coronagraphic imager at the Large Binocular Telescope, and argues that this software lets the instrument operate at full potential and is ready for regular science operations. A sympathetic reader would care because SHARK-NIR is designed to directly image exoplanets and circumstellar discs, and the paper ties the software's layered architecture—motor control, telescope tracking, adaptive-optics tip-tilt, detector readout, and observation sequencing—to the instrument's first published exoplanet results. The software's core is a C++ Observation Control Software component that dispatches commands to subsystems, implements hardware-collision avoidance, merges FITS headers, and exposes an interface used by Python template scripts and web GUIs. If SHINS works as described, it is a working example of how web-based, queue-style observing can control a high-contrast imager without low-level engineering intervention.

What carries the argument

The central object is obs_ctrl, the Observation Control Software: a C++ component built on the ICE middleware that connects at startup to all subsystem services, the telescope control interface, the power distribution unit, and the INDI-managed scientific camera. It stores the state of every device in dedicated objects updated at 1 Hz, with camera state updated by INDI events, and exposes both synchronous and asynchronous methods so high-level clients never block. It also hosts the three-layer anti-collision protection that blocks or aborts movements of the coronagraphic wheel when the calibration fiber deployer is in the forbidden region, and it merges the scientific camera's FITS header with a full instrument-status header. The second key object is the template and Observation Block layer: XML Observation Blocks name Python template scripts and their parameters, and a sequencer runs them through the obs_ctrl interface, so observers control complete procedures rather than individual devices.

What would settle it

Inspect the FITS headers of the HD 57625 and HIP 36277 observations in the telescope's archive: if those headers do not contain the merged instrument-status keywords produced by the obs_ctrl data-manager routine described in Section 5.4, then the early-science data were not produced by the described SHINS pipeline and the readiness claim would be falsified.

Watch

Extended reading notes

Core claim

The central claim is that SHINS is a complete, layered control system capable of running SHARK-NIR end to end: it controls the motorized wheels, stages, derotator, and atmospheric dispersion corrector through services built on a reuse-oriented motor-control framework; interfaces the scientific camera through the INDI protocol; manages the internal deformable-mirror loop and non-common-path aberration correction through the real-time computer; sequences observations through XML Observation Blocks executed by Python templates; and offers browser-based GUIs through REST APIs and websockets. The paper reports that early-science observations in coronagraphic mode with the Gaussian coronagraphic mask produced detections: a characterization of an eccentric giant planet around HD 57625 and deep imaging of three accelerating stars, with a candidate companion visible near HIP 36277. These results are presented as evidence that the software-enabled instrument achieves significant exoplanet science and is ready for regular operations.

Load-bearing premise

The claim that SHINS is ready for regular operations assumes that the software described in this paper is exactly the software that produced the early-science images, and the paper provides no version logs, configuration files, or revision identifiers to prove that connection.

Editorial extensions

If this is right

  • Observers can prepare a full night of observations with a wizard and run them from a browser-based Observation panel, with acquisition, calibration, and science steps sequenced automatically.
  • The anti-collision interlocks protect the coronagraphic wheel and fiber deployer even when an operator drives devices from engineering panels, so hardware safety does not depend on the user's expertise.
  • The NCPA strategy—a static deformable-mirror shape for internal aberrations plus a rotating shape sent every second for external aberrations—keeps the point spread function behind the coronagraph while the field derotates.
  • The same SHINS stack produced the early-science images cited in Section 9, so the software is not a design study but a system that has already delivered published astrophysical results.
  • Because Observation Blocks are XML and template scripts are parameterized Python, the same infrastructure can be extended to queue scheduling or remote operation without new low-level software.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • If the readiness claim survives, the SHINS architecture is a transferable template: the subsystem-control layer plus REST-and-websocket web layer could be adapted to other instruments with rotating mounts, since the paper separates hardware-specific services from generic sequencing.
  • The paper leaves open how the deployed configuration is versioned; checking FITS headers against the Section 5.4 merging scheme would close the gap between documentation and running code.
  • The observation-panel and wizard design hints at a future in which science users prepare and execute observing blocks without an instrument specialist at the telescope, a step the paper mentions as planned but does not develop.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 6 minor

Summary. The paper describes SHINS, the instrument control software for SHARK-NIR, a new near-infrared coronagraphic imager at the Large Binocular Telescope. It presents the hardware control layer (MoCon boards, PDU, detector electronics), the control network, subsystem services built on the TwiceAsNice framework, the central C++ Observation Control Software (obs_ctrl) over ICE, the sequencer/template/Observation Block execution layer, the REST API and web-based GUIs, and the data manager. Section 9 reports early-science coronagraphic images of HD 57625 and three accelerating stars, and the Conclusion asserts that SHINS is 'ready for regular operations.'

Significance. Assuming the architecture description is accurate, the paper is a valuable record of a deployed instrument control system and an example of substantial code reuse from LINC-NIRVANA and ARGOS. The layered design (TaN services, ICE-based obs_ctrl, Python sequencer, REST/web GUIs) is internally consistent and plausible, and the instrument has demonstrably produced science-grade images. The paper's strengths are its concrete architectural detail and its transparency about which components are internal versus public. Its main limitations are the absence of quantitative performance or reliability data and the lack of a direct link between the described software stack and the early-science observations cited as evidence for readiness.

major comments (3)
  1. [Section 9 and Conclusion] The statement that SHINS is 'ready for regular operations' is supported only by the early-science observations summarized in Section 9 and refs. [14,15], but the paper does not show that the software stack described in Sections 4-8 was the exact stack that executed those observations. There are no software revision identifiers, FITS-header keywords, configuration snapshots, or operator logs connecting the described TaN services, obs_ctrl, sequencer, REST API, or web panels to the 2024-02-21 HIP 36277 exposure (Fig. 20) or to the other cited runs. Section 8.3 states that the Wizard is an internal, not-yet-public tool whose OB directories are uploaded manually, and Section 8.4 says the Observation panel was created only after Commissioning, without a timeline tying it to the February 2024 data. Please explicitly identify which components were in the operational path on the dates of the cited observations (e.g., with a version table or timeline), or narrow the readiness claim to the specific components that were exercised.
  2. [Section 5.2] The anti-collision system is presented as a safety feature that protects the instrument from operator errors, described as 'fully transparent to final users' and as protecting against accidental errors via callbacks, but no validation evidence is reported. The paper gives neither a test campaign nor on-sky usage statistics for the three protection layers, and there is no failure-mode analysis (for instance, what happens if the callback thread is delayed or if a command arrives between the wheel's position check and the callback). Since the Conclusion's readiness claim depends on the software being safe for regular operations, the paper should at least summarize the tests of the anti-collision logic performed during AIT and commissioning.
  3. [General (performance evidence)] The paper provides no quantitative performance or reliability metrics for SHINS itself. For a software paper concluding operational readiness, it would be appropriate to report quantities such as command latencies, OB execution success/failure counts, system uptime, or the number of engineering and science templates run during commissioning and early science. Without such data, the 'ready for regular operations' claim is an assertion rather than a demonstrated result; adding a short evaluation subsection would considerably strengthen the paper.
minor comments (6)
  1. [Conclusion] The Conclusion states that SHINS 'exploits SNMP and INDI protocols to control the scientific camera and the calibration lamps, respectively,' but this reverses the assignments given in Section 5.1, where INDI controls the SCICAM and SNMP controls the lamps. Please correct the sentence or reword the 'respectively' clause.
  2. [Section 6] The word 'phyton' should be 'python' in the description of the sequencer.
  3. [Section 8] In the paragraph describing the typical observation flow, 'opearating' should be 'operating.'
  4. [Section 8.1] 'Rreadout parameters' should be 'Readout parameters.'
  5. [Table 1] In the Table 1 caption, 'trhough' should be 'through.'
  6. [Section 9] In the first sentence of Section 9, 'pupil-tabilized mode' should be 'pupil-stabilized mode,' and later 'the the contribution' contains a duplicated article.

Circularity Check

0 steps flagged · score 0.0 of 10

No circularity: SHINS is a descriptive software paper, and its readiness claim rests on external published early-science results and on the described architecture, not on fitted parameters or self-referential definitions.

full rationale

This paper does not attempt a predictive or first-principles derivation. It describes the architecture and implementation of an instrument control software and then reports early scientific results that were independently published in refereed journals (references [14] and [15]). The central claim—that SHINS operates SHARK-NIR and is ready for regular operations—is supported by the software description in Sections 4–8 and by the external early-science papers, not by re-using the same data as both input and output. The self-citations to prior SPIE proceedings ([16]–[19]) are incremental descriptions of the same development effort, and they are not used to justify a conclusion by definition or to forbid alternative explanations. The manuscript itself notes limitations, such as the wizard being 'for internal use of the SHARK-NIR team' (Section 8.3) and the Observation panel being created after Commissioning (Section 8.4), but these are evidence gaps about which interface was used during early science, not circular reasoning. No equation in the paper is fitted to data and then renamed a prediction; no parameter is defined in terms of the claimed result; and no uniqueness theorem is imported from the authors' prior work. The absence of logs or revision identifiers tying the described stack to the Section 9 observations weakens the readiness claim evidentially, but it does not make the argument circular. Accordingly, the appropriate circularity score is 0.

Assumptions & free parameters 0 free parameters · 3 assumptions · 0 invented entities

No new physical or formal entities are introduced; the paper repurposes existing software frameworks and hardware. The free-parameter list is empty because the paper makes no fitted or tunable-number claims. The axioms above are the unstated background assumptions that the described software works as specified and that the cited science results are valid.

assumptions (3)
  • domain assumption The TaN and ICE frameworks and MoCon board firmware function as documented by MPIA and Microgate.
    SHINS behavior depends on these external libraries and hardware behaving to specification, especially motor control via MoCon boards (Sections 2.1, 4).
  • domain assumption The early-science results in Section 9, published in refs [14,15], are accurate and were produced using the described SHINS software.
    The paper cites these as evidence of readiness without reproducing the analysis or linking runtime logs to the software configuration.
  • domain assumption The telescope interfaces (TCS IIF, INDI) provide the expected data and commands.
    obs_ctrl depends on TCS trajectory information and INDI camera events (Sections 4, 5.1).

how reviews work

0 comments
Cite this review

Pith. "Pith review of SHINS, the SHARK-NIR Instrument Control Software." pith.science (2026). https://pith.science/paper/CTZFNVS4

@misc{pith2026250419709,
  author       = {Pith},
  title        = {Pith review of: SHINS, the SHARK-NIR Instrument Control Software},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/CTZFNVS4}},
  note         = {Machine review of arXiv:2504.19709}
}
read the original abstract

SHARK-NIR is a new compact instrument for coronagraphic imaging, direct imaging, and coronagraphic spectroscopy in the near-infrared wavelengths mounted at LBT. Taking advantage of the telescope's adaptive optics system, it provides high contrast imaging with coronagraphic and spectroscopic capabilities and is focused on the direct imaging of exoplanets and circumstellar discs. We present SHINS, the SHARK-NIR instrument control software, mainly realized with the TwiceAsNice framework from MPIA - Heidelberg and the ICE framework using the C++ programming language. We describe how we implemented the software components controlling several instrument subsystems, through the adaptation of already tested libraries from other instruments at LBT, such as LINC-NIRVANA. The scientific detector comes with its own readout electronic and control software interfaced with our software through INDI. We describe the C++ core software Observation Control Software, responsible for dispatching commands to the subsystems, also implementing a software solution to avoid a potential collision between motorized components, fully transparent to final users. It exposes an ICE interface and can be controlled by clients developed in different languages. Observation, calibration, and maintenance procedures are implemented by means of template scripts, written in python language, controlling Observation Control Software through its ICE interface. These templates and their parameters are configured using "ESO-style", XML Observation Blocks prepared by observers, or in general SHARK-NIR users. The high-level control is carried out by REST HTTP APIs implemented in a python back-end, also acting as a web server for the several browser-based front-end GUIs. Finally, we present the first scientific results obtained by SHARK-NIR using coronagraphic mode.

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

29 extracted references · 28 canonical work pages

  1. [1]

    Pinna , S

    E. Pinna , S. Esposito , P. Hinz , et al. , `` SOUL: the Single conjugated adaptive Optics Upgrade for LBT ,'' in Adaptive Optics Systems V , E. Marchetti , L. M. Close , and J.-P. V \'e ran , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 9909 , 99093V (2016)

  2. [2]

    Pedichini , F

    F. Pedichini , F. Ambrosino , M. Centrone , et al. , `` The V-SHARK high contrast imager at LBT ,'' in Ground-based and Airborne Instrumentation for Astronomy VI , C. J. Evans , L. Simard , and H. Takami , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 9908 , 990832 (2016)

  3. [3]

    Viotto , J

    V. Viotto , J. Farinato , D. Greggio , et al. , `` SHARK-NIR system design analysis overview ,'' in Modeling, Systems Engineering, and Project Management for Astronomy VI , G. Z. Angeli and P. Dierickx , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 9911 , 991127 (2016)

  4. [4]

    Farinato , F

    J. Farinato , F. Bacciotti , C. Baffa , et al. , `` SHARK-NIR: from K-band to a key instrument, a status update ,'' in Adaptive Optics Systems V , E. Marchetti , L. M. Close , and J.-P. V \'e ran , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 9909 , 990931 (2016)

  5. [5]

    Farinato , C

    J. Farinato , C. Baffa , A. Baruffolo , et al. , `` The NIR arm of SHARK: System for coronagraphy with High-order Adaptive optics from R to K bands ,'' International Journal of Astrobiology 14 , 365--373 (2015)

  6. [6]

    Carolo , D

    E. Carolo , D. Vassallo , J. Farinato , et al. , `` SHARK-NIR coronagraphic simulations: performance dependence on the Strehl ratio ,'' in Optical and Infrared Interferometry and Imaging VI , M. J. Creech-Eakman , P. G. Tuthill , and A. M \'e rand , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 10701 , 107012B (2018)

  7. [7]

    Cerpelloni , E

    P. Cerpelloni , E. Carolo , G. Umbriaco , et al. , `` Unravelling the performance of the SHARK-NIR Four Quadrant Phase Mask in a controlled environment ,'' in Ground-based and Airborne Instrumentation for Astronomy X , J. J. Bryant , K. Motohara , and J. R. D. Vernet , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 13096...

  8. [8]

    Barbato , J

    D. Barbato , J. Farinato , A. Baruffolo , et al. , `` SHARK-NIR commissioning and early science runs ,'' in Ground-based and Airborne Instrumentation for Astronomy X , J. J. Bryant , K. Motohara , and J. R. D. Vernet , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 13096 , 130961W (2024)

Show all 29 references
  1. [9]

    Bergomi , L

    M. Bergomi , L. Marafatto , E. Carolo , et al. , `` SHARK-NIR: from design to installation, ready to dive into first light ,'' in Modeling, Systems Engineering, and Project Management for Astronomy X , G. Z. Angeli and P. Dierickx , Eds., Society of Photo-Optical Instrumentati...

  2. [10]

    Vassallo , M

    D. Vassallo , M. Bergomi , E. Carolo , et al. , `` Laboratory demonstration of focal plane wavefront sensing using phase diversity: a way to tackle the problem of NCPA in SHARK-NIR: Part II: new characterization tests and alternative wavefront sensing strategies ,'' in Adaptiv...

  3. [11]

    Umbriaco , D

    G. Umbriaco , D. Vassallo , J. Farinato , et al. , `` Deformable lens for testing the performance of focal plane wavefront sensing using phase diversity ,'' in Adaptive Optics Systems VIII , L. Schreiber , D. Schmidt , and E. Vernet , Eds., Society of Photo-Optical Instrumenta...

  4. [12]

    Farinato , A

    J. Farinato , A. Baruffolo , M. Bergomi , et al. , `` SHARK-NIR, ready to ``swim'' in the LBT Northern Hemisphere ``ocean'' ,'' in Adaptive Optics Systems VIII , L. Schreiber , D. Schmidt , and E. Vernet , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Confere...

  5. [13]

    Marafatto , E

    L. Marafatto , E. Carolo , G. Umbriaco , et al. , `` SHARK-NIR on its way to LBT ,'' in Ground-based and Airborne Instrumentation for Astronomy IX , C. J. Evans , J. J. Bryant , and K. Motohara , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series...

  6. [14]

    Barbato , D

    D. Barbato , D. Mesa , V. D'Orazi , et al. , `` A multi-technique detection of an eccentric giant planet around the accelerating star HD 57625 ,'' 693 , A81 (2025)

  7. [15]

    Mesa , R

    D. Mesa , R. Gratton , V. D'Orazi , et al. , `` Deep imaging of three accelerating stars using SHARK-NIR and LMIRCam at LBT ,'' 536 , 1455--1466 (2025)

  8. [16]

    Lorenzetto, D

    A. Lorenzetto, D. Ricci, F. Laudisio, et al. , `` SHARK-NIR instrument control software: new features and tools approaching science runs ,'' in Software and Cyberinfrastructure for Astronomy VIII , J. Ibsen and G. Chiozzi, Eds., 13101 , 131013S, International Society for Optic...

  9. [17]

    Ricci , F

    D. Ricci , F. Laudisio , S. Chavan , et al. , `` Improvements to SHINS, the SHARK-NIR instrument software, during the AIT phase ,'' in Software and Cyberinfrastructure for Astronomy VII , Society of Photo-Optical Instrumentation Engineers (SPIE) Conference Series 12189 , 12189...

  10. [18]

    De Pascale , A

    M. De Pascale , A. Baruffolo , B. Salasnich , et al. , `` SHARK-NIR: implementation of the instrument control software SHINS ,'' in Software and Cyberinfrastructure for Astronomy VI , J. C. Guzman and J. Ibsen , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) C...

  11. [19]

    De Pascale , A

    M. De Pascale , A. Baruffolo , B. Salasnich , et al. , `` Design of SHINS: the SHARK-NIR instrument control software ,'' in Software and Cyberinfrastructure for Astronomy V , J. C. Guzman and J. Ibsen , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) Conference...

  12. [20]

    T. M. Herbst , R. Ragazzoni , A. Eckart , et al. , `` LINC-NIRVANA: the Fizeau interferometer for the Large Binocular Telescope ,'' in Optical and Infrared Interferometry , M. Sch \"o ller , W. C. Danchi , and F. Delplancke , Eds., Society of Photo-Optical Instrumentation Engi...

  13. [21]

    Berwein , F

    J. Berwein , F. Briegel , W. Gaessler , et al. , `` An SOA developer framework for astronomical instrument control software ,'' in Advanced Software and Control for Astronomy II , A. Bridger and N. M. Radziwill , Eds., Society of Photo-Optical Instrumentation Engineers (SPIE) ...

  14. [22]

    Rabien , R

    S. Rabien , R. Angel , L. Barl , et al. , `` ARGOS at the LBT. Binocular laser guided ground-layer adaptive optics ,'' 621 , A4 (2019)

  15. [23]

    J. M. Leisenring , M. F. Skrutskie , P. M. Hinz , et al. , `` On-sky operations and performance of LMIRcam at the Large Binocular Telescope ,'' in Ground-based and Airborne Instrumentation for Astronomy IV , I. S. McLean , S. K. Ramsay , and H. Takami , Eds., Society of Photo-...

  16. [24]

    Vassallo , J

    D. Vassallo , J. Farinato , J. F. Sauvage , et al. , `` Validating the phase diversity approach for sensing NCPA in SHARK-NIR, the second-generation high-contrast imager for the Large Binocular Telescope ,'' in Modeling, Systems Engineering, and Project Management for Astronom...

  17. [25]

    R. T. Fielding and R. N. Taylor, Architectural styles and the design of network-based software architectures . PhD thesis, University Of California, Irvine (2000). AAI9980887

  18. [26]

    Ricci , L

    D. Ricci , L. Cabona , B. Salasnich , et al. , `` Easy remote observations using web interfaces: controlling an Italian telescope from Japan, and more ,'' in Observatory Operations: Strategies, Processes, and Systems X , C. R. Benn , A. Chrysostomou , and L. J. Storrie-Lombard...

  19. [27]

    Ricci , L

    D. Ricci , L. Cabona , S. Tosi , et al. , `` Toward the remotization and robotization of the OARPAF Telescope ,'' in Observatory Operations: Strategies, Processes, and Systems IX , D. S. Adler , R. L. Seaman , and C. R. Benn , Eds., Society of Photo-Optical Instrumentation Eng...

  20. [28]

    Rouan , P

    D. Rouan , P. Riaud , A. Boccaletti , et al. , `` The Four-Quadrant Phase-Mask Coronagraph. I. Principle ,'' 112 , 1479--1486 (2000)

  21. [29]

    write newline

    " write newline "" before.all 'output.state := FUNCTION blank.sep after.quote 'output.state := FUNCTION fin.entry output.state after.quoted.block = 'skip 'add.period if write newline FUNCTION new.block output.state before.all = 'skip output.state after.quote = after.quoted.blo...

Pith tools

Reviewed August 16, 2026 · model on record in the stance chip above.