The INPUT Field Does the Heavy Lifting
The INPUT field in RAD AMT is a plain text field — but the way you structure the string determines everything about what the RESULTS [RADIATION AMT] JS field can return. Feed it a raw dose value and unit (e.g., "5 mGy" or "200 mSv") and the JS computes the corresponding absorbed dose, equivalent dose, or effective dose depending on the radiation weighting factors encoded in the script. Feed it a source activity in becquerels and an exposure time, and you get the integrated dose for that exposure window.
This is not a general-purpose calculator. It's designed for a specific workflow: rapid field calculations where the researcher knows exactly what they're inputting and needs the answer in the record, not on a napkin. The lack of a separate label field is intentional — the INPUT string carries the context. Parse it consistently and your database is both a log and an audit trail.
What the JavaScript Layer Computes
The RESULTS [RADIATION AMT] JS field handles unit conversion and regulatory threshold flagging. Standard practice in most dosimetry contexts is to work in millisieverts for effective dose to personnel and in gray for absorbed dose to material or tissue. The JS output normalizes to both, then flags the result against the annual occupational limit (20 mSv/year for most jurisdictions following ICRP 103) and the public dose limit (1 mSv/year).
This flag is the operational core of the template. During a research campaign involving repeated small exposures — routine calibration source handling, beam alignment checks, sample preparation in hot cells — the individual dose events look trivial. The JS flag catches when cumulative dose across multiple entries is approaching the quarterly fraction of the annual limit. The individual record is fine. The aggregate isn't.
Scaling to a Full Research Campaign
At 50 entries spanning a multi-week experiment, the RAD AMT database is a complete dosimetry log. Sorted by date, it shows every recorded exposure event in order. Filtered by source type within the INPUT string, it shows the dose contribution from each radiation source independently — useful when you're working with both alpha-emitting calibration sources and a beta-emitting tracer in the same campaign and need to separate them for reporting to your radiation safety officer.
At 200 entries over a full research year, you have the data backbone for your annual ALARA review. The JS-computed effective dose values aggregate into a total. The regulatory threshold flags tell you which months came closest to limits. The INPUT strings record exactly what you were doing. That's not a reconstructed estimate — it's a contemporaneous record with timestamps.