Problem with importing channel from Citadel

[Ermak]

Hi,

I am trying to import a channel from Citadel into Diadem usign the data store capability.

I have data from February to June in Citadel, but I only get data from February to March in the Diadem.

This is a new issue for me, and what makes it really interesting is that I was able to import all the data yesterday, but not today.

Do you know what might be the problem?

Thank you

Egor

[Brad_Turpin]

Hi Egor,

When you are importing data from Citadel into DIAdem using the data store approach, are you requesting a specific date range, or are you requesting all the data in the server?  Also, are you requesting the data as native deadbanded XY pairs, or are you asking it to be delivered with a specific target acquisition period?  Are your settings in the Citadel data store dialog exactly the same today as they were a few days ago?

This is a very stable and successful import method, I have no knowledge of any prior malfunction of this type.

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Ermak]

Hi Brad,

I am not setting a specific date range for the imported data. The settings in Citadel are exactly the same, I did not modify anything.

What do you mean by "native deadbanded XY pairs" ?

The procedure I use is as follows:

1. Open a datastore.

2. Choose  a channel.

3. Load data.

And I only get a portion of the data.

Note that I have over 1 million points in a channel.

Also, if I choose channel properties in DIAdem, I have the following:

measurement_begin: 02/23/2009 08:52:14

measurement_end: 06/04/2009 22:40:27

But I am only able to see the data until 03/18/2009

[Brad_Turpin]

Hi Egor,

Wow, that's a lot of trace data-- I've never tried to load that much from Citadel before.  If the data store settings in the dialog have not changed from last week to now, can you think of anything else that has changed?  For instance, it sounds like there is not a huge difference in the amount of data stored in the Citadel data base from last week to this week.  Have you installed any software on that computer in the last week-- applications or updates or drivers or anything?

What happens if you ask for a very narrow datetime ratio from, say, April?  If you make the datetime range narrow enough, do you ever get all the data points?  What happens if you configure the data store settings in the dialog to return the data as if it were measured one point per hour (3600 sec)-- dou you get all the data then?  I'm curious if the problem has to do with requesting too much data for the import-- I don't really know what the upper limit is.

How much RAM do you have on this computer?

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Ermak]

Hi Brad,

No settings were changed and no drivers installed.

When I use a more narrow time range, I am able to import the data between the specified times. Note that when i am trying to import all data, I obtain about 200000 points, but when i choose to import data between April and June, i obtain more than 400000 points.

Also, I played with time stamps a bit and I noticed that I data usually stops at 1 of April, i.e when I import data between February and April, it will stop at Aptil 1st. When I import data between March and April, the data will stop at April 1st.  However, when I import the data beyond april 1st, i get all the points (beyond April 1st).

This is very weird, concidering the fact that everything worked last week.

Thank you

Egor

[Brad_Turpin]

Hi Egor,

I agree that this is weird.  It seems like you have ruled out the possibility that the problem is simply requesting too much data from Citadel at one time, since the failure tracks with spanning April 1, not with the amount of data points requested.  Would you be willing to send us the Citadel data base for R&D to take a look at?  If so, you should post your data base to the ftp site, then send me an email telling me the file name that you posted.

Brad Turpin

DIAdem Product Support Engineer
National Instruments

brad.turpin@ni.com

[Ermak · Accepted solution]

Hi Brad,

The problem was fixed. It turns out that one of the zip files with .cdpg files was corrupted. In fact that file contained the April 1st data.

When I replaced it with a back up file, DIAdem was able to import all the data from Citadel.

Thanks,

Egor