Mike Swanson
45083f4735
Extends the Test Datasheet Pipeline on AD2:C:\Shares\testdatadb to
generate web-published datasheets for the SCMVAS-Mxxx (obsolete) and
SCMHVAS-Mxxxx (replacement) High Voltage Input Module product lines.
Both are tested either with the existing TESTHV3 software (production
VASLOG .DAT logs) or in Engineering with plain .txt output.
Key changes on AD2 (all deployed 2026-04-12 with dated backups):
- parsers/spec-reader.js: getSpecs() returns a `{_family:'SCMVAS',
_noSpecs:true}` sentinel for SCMVAS/SCMHVAS/VAS-M/HVAS-M model prefixes
so the export pipeline does not silently skip them for missing specs.
- templates/datasheet-exact.js: new Accuracy-only template branch
(generateSCMVASDatasheet + helpers) that mirrors the existing shipped
format byte-for-byte. Extraction regex covers both QuickBASIC STR$()
output formats: scientific-with-trailing-status-digit (98.4% of
records) and plain-decimal (1.6% of records above QB's threshold).
- parsers/vaslog-engtxt.js (new): parses the Engineering-Tested .txt
files in TS-3R\LOGS\VASLOG\VASLOG - Engineering Tested\. Filename SN
regex strips optional trailing 14-digit timestamp; in-file "SN:"
header is the authoritative source when the filename is malformed.
- database/import.js: LOG_TYPES grows a VASLOG_ENG entry with
subfolder + recursive flags. Pre-existing 7 log types keep their
implicit recursive=true behaviour (config.recursive !== false).
importFiles() routes VASLOG_ENG paths before the generic loop so a
VASLOG - Engineering Tested/*.txt path does not mis-dispatch to the
multiline parser.
- database/export-datasheets.js: VASLOG_ENG records are written
verbatim via fs.copyFileSync(source_file, For_Web/<SN>.TXT) for true
byte-level pass-through, with a graceful raw_data fallback when the
source file is no longer on disk.
Deploy outcome:
- 27,503 SCMVAS/SCMHVAS datasheets rendered (27,065 from scientific +
438 from plain-decimal PASS lines, post-patch rerun)
- 434 Engineering-Tested .txt files pass-through-copied to For_Web
- 0 errors across both batches
Repo layout added here:
- scmvas-hvas-research/: discovery artifacts (source .BAS, hvin.dat,
sample .DAT + .txt, binary-format notes, IMPLEMENTATION_PLAN.md)
- implementation/: staged final code + deploy helpers + local test
harness + per-step verification scripts
- backups/pre-deploy-20260412/: independent local snapshot of the 4
AD2 files replaced, pulled byte-for-byte before deploy
All helper scripts fetch the AD2 password at runtime from the SOPS
vault (clients/dataforth/ad2.sops.yaml). None of the committed files
contain the plaintext credential. Known vault-entry hygiene issue
(stale shell-escape backslash before the `!`) is documented in the
fetcher comments and stripped at read-time; flagged separately for
cleanup.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
High Input Voltage Units test program directory containing the archived and
release versions of the test and database programs.
Directory structure:
HVDATA: Current version of the high input voltage database file ("hvin.dat") is in this directory, while the archived previous versions are under the "History" subdirectory ("...\HVU\HVDATA\History").
Release: The current released test program source files and executable are in this directory, while the archived previous versions are under the "History" subdirectory ("...\HVU\Release\History").
DBpgm: The current released high input voltage database modification program source files and executable are in this directory, while the archived previous versions are under the "History" subdirectory ("...\HVU\DBpgm\History").
NOTE: The ongoing structure and naming convention for the archived ("history") files should include ALL of the source files (including the ".MAK" file) and the executable file for that version of the program, which should be located in a folder named for the date of release in this format: "year-month-date" with a four-digit year, two digit month (leading zero if required), and a two-digit date (leading zero if required). For example, "2014-07-31" for July 31, 2014. Maintaining this format will lead to consistent sorting when attempting to locate versions in the future. This folder should be created under the appropriate "History" subfolder (under "...\HVU\DBpgm\History" for database programs, ...\HVU\Release\History" for test programs, or "...\HVU\HVDATA\History" for database files.
FURTHER NOTE: Previously archived test and/or database programs do not necessarily follow the structure described above, and are all located under the "...\HVU\Released\History\_Old (Pre 2014-07-31)" folder.
Program release instructions:
-----------------------------
The updated test program executable (.EXE) file is copied to:
"T:\ENGR\ATE\ProdSW\ATE"
Then the batch file "TtoK.bat" is run (double-click on the file name in Window Explorer) in folder:
"T:\ENGR\ATE\ProdSW\ATE Software Transfer Programs"
Database release instructions:
-----------------------------
The updated test database (.DAT) file is copied to:
"T:\ENGR\ATE\ProdSW\ATE\HVDATA"
Then the batch file "TtoK.bat" is run (double-click on the file name in Window Explorer) in folder:
"T:\ENGR\ATE\ProdSW\ATE Software Transfer Programs"