Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#18 closed defect (fixed)

Sample buffer is not loaded automatically from database

Reported by: titus_franzmann Owned by: demeler
Priority: normal Milestone:
Component: Analysis Version:
Keywords: Cc:

Description

I recently made several runs with different buffers. I added the buffers individually to the uslims-database and assigned my experimental data with the buffer accordingly. When I view my result datain FE, the buffer conditions loaded is always that of cell one. When I now load a 2-DSA, GA, etc. model for cell 2 then the fit does not match the experimental data. Apparently, this is because the buffer condition is not correct. I assume this is a visualizing issue. Assigning the correct buffer before loading the model, fixes this issue. Apparently, the buffers are correctly assigned on uslims, however in ultrascan this information has to be updated manually. Which apparently appears to be a problem with runs that had been carried out a while ago and must be reviewed.

Change History (4)

comment:1 follow-up: Changed 11 years ago by demeler

  • Status changed from new to assigned

Titus,

please tell us what dataset had this issue. Please make sure the data are in the database, together with some models to test.

Thanks, -b.

comment:2 in reply to: ↑ 1 Changed 11 years ago by demeler

Replying to demeler:

Titus,

please tell us what dataset had this issue. Please make sure the data are in the database, together with some models to test.

Thanks, -b.

Titus writes:

I uploaded the entire dataset and analysis incl. the models to uslims. Experimental ID: 104 Run ID: dCrys_Gdm2 Please note that I am using the Windows Version of UltraScan?. Best wishes Titus

I loaded the run under Linux and was able to confirm that the buffer information is stuck on cell 1, even though there are 3 different buffers correctly defined in the raw data. This appears to be an error with the data_io logic, and I will investigate this.

-b.

comment:3 follow-up: Changed 11 years ago by demeler

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

This problem has been fixed. Since this is a major problem with the viewer I would like to make a new release for UltraScan? 9.9, revision 708 (or higher, if Emre or Bruce have something else to add).

Please prepare new binaries for all platforms.

Thanks, -Borries

comment:4 in reply to: ↑ 3 Changed 11 years ago by emre

I have nothing to add at this time. FYI - There will likely be a new release for 'SOMO'-beta in another two weeks.

Note: See TracTickets for help on using tickets.