Ticket #4852 (closed: worksforme)

Opened 9 years ago

Last modified 5 years ago

[IndDiff] - Track down source of errant error messages

Reported by: Peter Parker Owned by: Peter Parker
Priority: minor Milestone: Release 3.0
Component: Indirect Inelastic Keywords: IndDiff
Cc: Blocked By:
Blocking: Tester: Jay Rainey

Description (last modified by Peter Parker) (diff)

Run the following in the Python console (or use the Indirect Diffraction interface):

OSIRISDiffractionReduction(Sample="89770,89771,89772,89773,89774,89775", 
Vanadium="92257,92258,92259,92260,92261,92262", CalFile="osiris_041_RES10.cal", 
OutputWorkspace="test")

The results log will display several errors of the following form:

Cannot open ICPevent file C:\test/OSI92261_ICPevent.txt. Period 1 assumed for all data.
Unable to open file C:\test/OSI92261_CCR.txt
Unable to open file C:\test/OSI92261_ICPdebug.txt
Unable to open file C:\test/OSI92261_ICPevent.txt
Unable to open file C:\test/OSI92261_ICPstatus.txt
Unable to open file C:\test/OSI92261_Sample.txt
Unable to open file C:\test/OSI92261_Status.txt
Unable to open file C:\test/OSI92261_Stick.txt

The errors only display for certain runs (89774/92261 and 89775/92262).

Setting as minor as this does not seem to stop the algorithm or have any negative side effects.

Change History

comment:1 Changed 9 years ago by Peter Parker

  • type changed from enhancement to defect

comment:2 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.1 to Release 2.2

Moved at end of release 2.1

comment:3 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

comment:4 Changed 8 years ago by Peter Parker

  • Keywords IndDiff added

comment:5 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to release 2.4

comment:6 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.4 to Release 2.5

Moved at the code freeze for release 2.4

comment:7 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.5 to Release 2.6

Moved to r2.6 at the end of r2.5

comment:8 Changed 7 years ago by Nick Draper

  • Component changed from Mantid to Framework

comment:9 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.6 to Backlog

Moved to the Backlog after the code freeze for R2.6

comment:10 Changed 7 years ago by Peter Parker

  • Status changed from new to verify
  • Resolution set to worksforme
  • Description modified (diff)
  • Milestone changed from Backlog to Release 3.0

This was a minor annoyance reported by Franz many moons ago, who was concerned about error messages that didn't have any relevance to -- and couldn't be fixed by -- him as a user.

I'm not sure which changeset has addressed this in the meantime, but I no longer see the error messages he originally pointed out. There are still some error messages when running the script (using the data files in the system test directory), but these are to do with invalid detector IDs in the given calibration file and so are at least meaningful a user who has provided the input files.

I think we can probably close this ticket now.

comment:11 Changed 7 years ago by Jay Rainey

  • Status changed from verify to verifying
  • Tester set to Jay Rainey

comment:12 Changed 7 years ago by Jay Rainey

  • Status changed from verifying to closed

comment:13 Changed 7 years ago by Jay Rainey

I also no longer see the error messages originally pointed out.

comment:14 Changed 7 years ago by Nick Draper

  • Component changed from Framework to Indirect Inelastic

comment:15 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 5699

Note: See TracTickets for help on using tickets.