Opened 5 years ago

Closed 3 years ago

#563 closed bug (fixed)

integer too large for monitor count field

Reported by: srkline Owned by: srkline
Priority: major Milestone: VSANS File Definition
Component: All Components Keywords:
Cc: Blocking:
Task:

Description

when copying VCALC to a VSANS file, using a value of iMon (= neutrons on sample) for the simulation, and putting this value into the control/monitor_counts field, I found that 1e9 was fine, but writing 1e10 was read back in as 1.41e9. This will need some further investigation whether this is a size limitation of the field, bug, or other error. Or does the field even need to carry a number that large?

Change History (2)

comment:1 Changed 4 years ago by srkline

what are the typical values for say, a 3600 second run with the white beam configuration? This would likely be a "worst case"

comment:2 Changed 3 years ago by srkline

  • Resolution set to fixed
  • Status changed from new to closed

for the white beam, the MCR is < 10,000 cts/s. So a 3600 second run would have a monitor count of 3.6E7 counts, which is perfectly fine.

so for now, this doesn't appear to be an issue

Note: See TracTickets for help on using tickets.