LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

managing measurements and lvoop

Hello,

I realise a calibration application using lvoop

 

I created class for device and class for xy data containing arrays of mesurements. For the moment devices and class are linked using index. I mean when i realise measurment i have a list of devices and list of xy data so to know wich devices provided wich measurements i use index.

 

I feel that adding xydata as a property of device could strengten coherence but i’m asking to myslef what impact it could have regarding performance. Because each time i will have to pass a device , attached mesurement will follow.

Do you suggest me to create a reference as property of device pointing on xy data or adding xy data class as a component of device class  ?

 

Regards

 

Tinnitus

CLAD / Labview 2011, Win Xp
------------------------------------------------------
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail

Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte
0 Kudos
Message 1 of 2
(2,194 Views)

Tinnitus,

 

I do something remarkably similar.  I have a generic instrument class which is inherited by a variety of different instrument types.  Each Instrument class carries with it a generic "Data" class which in-turn is the parent of data classes specific to the particular instrument.  I run fairly high performance applications (that do things such as collect AI at ~2.5 MS/s, perform fits on the data, etc, etc) and I have noticed no major performance issues.  That being said - adding an xy data property will increase the memory footprint of the device class. But, I like this approach.  Just my two cents.

 

Cheers, Matt

0 Kudos
Message 2 of 2
(2,187 Views)