Opened 9 years ago

Closed 9 years ago

#212 closed defect (fixed)

noise-model ID linkage in DB

Reported by: gegorbet Owned by: bdubbs
Priority: normal Milestone: 1.0
Component: ultrascan3 Version: 1.0
Keywords: review Cc:

Description

In tracing an apparent problem in the noise loader, I found that the get_model_desc API was the culprit. The noise loader problem was that 10 noises were presented in the tree for a single model; something that should not happen. In fact, the noises were from separate models of a back end fit-meniscus run.

The get_model_desc API used in the noise loader gets the same model ID value for each of the noises. So, there appears to be a problem with this API, with the DB linkages, with the load of models and noises after a back end fit-meniscus run, or with some combination of all of them.

The DB records in question are from cauma3 under investigator demeler. The models are IDs 80-89 and the noises IDs 81-90. Note that the models have identical description strings and time stamps, but that they differ in ID, GUID, and content. Internally (XML content), the noises each have parent model GUIDs that are unique.

Change History (3)

comment:1 Changed 9 years ago by bdubbs

  • Owner changed from dzollars to bdubbs
  • Status changed from new to assigned

I think this is the problem we found last night where the noise table was not being updated with the correct model ID. The fix I made was incorrect and causes an error, but I suspect when it is fixed, this problem will go away.

comment:2 Changed 9 years ago by bdubbs

  • Keywords review added

We may need to clean out the DB to test this, but I think it's fixed for new runs.

comment:3 Changed 9 years ago by dzollars

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.