AIDA GELINA BRIKEN nToF CRIB ISOLDE CIRCE nTOFCapture DESPEC DTAS EDI_PSA 179Ta CARME StellarModelling DCF K40
  DESPEC  ELOG logo
Entry  Mon Nov 4 13:17:12 2019, NH, Report: aida10 database corruption db_working.txtdb_corrupt.txt
    Reply  Tue Nov 5 10:02:45 2019, NH PJCS, Report: aida10 database corruption 
       Reply  Tue Nov 5 10:32:21 2019, NH PJCS, Report: aida10 database corruption 
          Reply  Tue Nov 5 11:15:41 2019, NH PJCS, Report: aida10 database corruption 
Message ID: 89     Entry time: Tue Nov 5 11:15:41 2019     In reply to: 88
Author: NH PJCS 
Subject: Report: aida10 database corruption 

If ypou now check the actual values in the aida10 Options screen are the correct ?

It can happen that corruptions once loaded are propagated when Options are generally saved. 

Looking at the dates the files were modified does that make sense to you. It doesn't look as if the corrupted database was changed except when they all were ? Can you check ? Have you checked the other Options files ? I seem to recall that RIKEN AIDA had a program to to this ?

Quote:

Hi, see the attached files in the original comment. I think the BACKUPCorrupt is quite old now.

The Options data gets corrupted and for example the ASIC folder gets set to 'undefined' which I think is why the ASIC data loads incorrectly.

 

Quote:

This looks like the Options not the ASIC data. That will be in the CONTENTS file of the FEE64 named directory within the dated EXPERIMENT directory. Looks like the latest is at /MIDAS/DB/EXPERIMENTS/AIDA/2019Oct31-13.24.23/aida10 ?

A quick look at this file and it looks normal , not all 0xad ? 

Looked at the Options file in the /MIDAS/DB/EXPERIMENTS/AIDA/Options.BACKUPCorrupt/aida10 and the worst bit is the name of the Data Acquistion program.  That could welll cause you problems with readout as it won't understand some of the new data.

 

Quote:

Often aida10 database seems to get corrupted (ASIC values are all 0xad)
Unsure why it's only aida10, might be related to weird alpha rate behaviour at the moment.

 

Attached is corrupted database and correct database

 

 

 

ELOG V3.1.4-unknown