It's that collect, store & simultaneously display thing. You're right, a database certainly would cure the problem. In fact, if the dataset is going to get huge it would be a much better idea. Would also really help crank up efficiency too.
Then again, sometimes a minimalist approach is enough of a demo to get the check Plenty of time to worry about a database after the gas tank is full!
My my. Three years ago I would have said, "...after there's bread on the table."
-SHAWN-
> -----Original Message-----
> From: Warren, Rufus [mailto:Rufus.Warren@Herley.Com]
> Sent: Friday, June 27, 2008 3:23 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
>
> Shawn,
>
> I'm not sure what you guys are trying to do, but it looks like someone
> needs to use a data base with multiple accesses.
>
> Rufus
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
> Sent: Friday, June 27, 2008 4:14 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
> I don't think this is going to get you there.
>
> Basically, I see two problems. One is synchronization. You've got two
> threads trying to access the same file. VEE uses one file pointer for
> each unique file. IOW, there's only one file pointer for both files,
> so when the threads go out of sync something is going to break.
>
> Second is "clear file at open". Every time this file is opened it's
> cleared.
> Certainly not what you want.
>
> What you need IMO is a client/server architecture. The server collects
> data & writes it to an accumulator file and the client reads &
> displays data.
> Two separate programs. Two separate file pointers.
>
> Unfortunately, you can't use sharing so file access has to be guarded.
> In
> VEE terms, it's probably simplest to put an error output on the file
> access objects & simply delay for a short period when you get a
> sharing violation.
>
> If you expect this to run for a long time error pins can be a problem.
> When
> I ran across this I got roughly 300,000 error pings before VEE lost
> it's cookies.
>
> If you want to use API functionality directly, you could easily do the
> whole thing in one program but then you wouldn't be able to use
> datasets, so that might be more trouble than it's worth.
> -SHAWN-
>
>
>
>
> ---
> You are currently subscribed to vrf as: Rufus.Warren@herley.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com"
> with the word subscribe in the message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>
>
> The information contained in this message may be confidential and
> legally privileged. If you are not the intended recipient of this
> email and its attachments, you must take no action based upon them,
> nor must you copy or show them to anyone.
> Please contact the sender if you believe you have received this email
> in error.
>
>
>
>
>
> ---
> You are currently subscribed to vrf as: shawn@vrfarchive.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com" with the word subscribe in the
> message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>
Then again, sometimes a minimalist approach is enough of a demo to get the check Plenty of time to worry about a database after the gas tank is full!
My my. Three years ago I would have said, "...after there's bread on the table."
-SHAWN-
> -----Original Message-----
> From: Warren, Rufus [mailto:Rufus.Warren@Herley.Com]
> Sent: Friday, June 27, 2008 3:23 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
>
> Shawn,
>
> I'm not sure what you guys are trying to do, but it looks like someone
> needs to use a data base with multiple accesses.
>
> Rufus
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
> Sent: Friday, June 27, 2008 4:14 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
> I don't think this is going to get you there.
>
> Basically, I see two problems. One is synchronization. You've got two
> threads trying to access the same file. VEE uses one file pointer for
> each unique file. IOW, there's only one file pointer for both files,
> so when the threads go out of sync something is going to break.
>
> Second is "clear file at open". Every time this file is opened it's
> cleared.
> Certainly not what you want.
>
> What you need IMO is a client/server architecture. The server collects
> data & writes it to an accumulator file and the client reads &
> displays data.
> Two separate programs. Two separate file pointers.
>
> Unfortunately, you can't use sharing so file access has to be guarded.
> In
> VEE terms, it's probably simplest to put an error output on the file
> access objects & simply delay for a short period when you get a
> sharing violation.
>
> If you expect this to run for a long time error pins can be a problem.
> When
> I ran across this I got roughly 300,000 error pings before VEE lost
> it's cookies.
>
> If you want to use API functionality directly, you could easily do the
> whole thing in one program but then you wouldn't be able to use
> datasets, so that might be more trouble than it's worth.
> -SHAWN-
>
>
>
>
> ---
> You are currently subscribed to vrf as: Rufus.Warren@herley.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com"
> with the word subscribe in the message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>
>
> The information contained in this message may be confidential and
> legally privileged. If you are not the intended recipient of this
> email and its attachments, you must take no action based upon them,
> nor must you copy or show them to anyone.
> Please contact the sender if you believe you have received this email
> in error.
>
>
>
>
>
> ---
> You are currently subscribed to vrf as: shawn@vrfarchive.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com" with the word subscribe in the
> message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
No that isn't what I'm after. The idea is that data gets collected into a dataset, the datafile gets rewound, and then ALL data gets read into an array of records - the do object is necessary here for this.
Removing the do object (and the rewind pin) results in only the last data point being read. I also get an error if I uncheck the "clear file at pre-run" option.
--
Kevin Nievaart
Materials Testing Officer
Dept. Civil Engineering
Monash University, Clayton Campus
Ph. (03) 9905-1165
Fax (03) 9905-1483
"It is known that there is an infinite number of worlds, simply because there is an infinite amount of space for them to be in. However, not every one of them is inhabited. Therefore, there must be a finite number of inhabited worlds. Any finite number divided by infinity is as near to nothing as makes no odds, so the average population of all the planets in the universe can be said to be zero. From this it follows that the population of the universe is also zero, and that any people you may meet from time to time are merely the product of a deranged imagination." - Douglas Adams
SHAW,JIANN-DER (A-Taiwan,ex1) wrote:
> Hi Kevin,
>
> Just simply remove "do" object and un-check the clear file in dataset object.
> Please check if this is what you expected?
>
>
> Best regards,
> Jiann-Der Shaw
>
> Application Engineering Organization
> Agilent Technologies
> IDD: 886-3-4959344
> Telnet: 846-3344
> Mobile: 886-917672043 (0917672043 in Taiwan)
>
>
>
>
> -----Original Message-----
> From: Kevin Nievaart [mailto:Kevin.Nievaart@eng.monash.edu.au]
> Sent: Wednesday, June 25, 2008 10:37 AM
> To: PDL-LISTS,VRF (A-Lists,unix1)
> Subject: [vrf] records and datasets
>
> G'day vrf'ers,
> I'm having an issue with writing to and reading from datasets. I'd like to be able to dynamically display an x vs y graph. The issue is, I'd like to be able to read from the dataset while its being written to.
> The idea is to be able to graph 1 field against time, and mid test, be able to see the graph of a different field against time. In order for this to work, I need to be able to:
>
> * write the latest data to the end of the dataset
> * rewind the file
> * read the entirety of the dataset
> * repeat
>
> I'd like to do it like this as there are 30 fields I'd like to potentially see.
>
> Nothing is working for me at the moment. In the attached vee file, I've set up a simple 3 field dataset, and this program attempts to do the above steps. However the green counter never gets above 6 before the whole thing stops working. (the dataset output just constantly out puts 0's for all 3 fields.) Any suggestions?
> Cheers,
>
>
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
I'm using VEE 7.5 on a winxp sp2 box
--
Kevin Nievaart
Materials Testing Officer
Dept. Civil Engineering
Monash University, Clayton Campus
Ph. (03) 9905-1165
Fax (03) 9905-1483
"It is known that there is an infinite number of worlds, simply because there is an infinite amount of space for them to be in. However, not every one of them is inhabited. Therefore, there must be a finite number of inhabited worlds. Any finite number divided by infinity is as near to nothing as makes no odds, so the average population of all the planets in the universe can be said to be zero. From this it follows that the population of the universe is also zero, and that any people you may meet from time to time are merely the product of a deranged imagination." - Douglas Adams
Kevin Nievaart wrote:
> G'day Jiann-Der,
> No that isn't what I'm after. The idea is that data gets collected
> into a dataset, the datafile gets rewound, and then ALL data gets read
> into an array of records - the do object is necessary here for this.
> Removing the do object (and the rewind pin) results in only the last
> data point being read. I also get an error if I uncheck the "clear
> file at pre-run" option.
>
> --
> Kevin Nievaart
> Materials Testing Officer
>
> Dept. Civil Engineering
> Monash University, Clayton Campus
> Ph. (03) 9905-1165
> Fax (03) 9905-1483
>
>
> "It is known that there is an infinite number of worlds, simply
> because there is an infinite amount of space for them to be in.
> However, not every one of them is inhabited. Therefore, there must be
> a finite number of inhabited worlds. Any finite number divided by
> infinity is as near to nothing as makes no odds, so the average
> population of all the planets in the universe can be said to be zero.
> From this it follows that the population of the universe is also zero,
> and that any people you may meet from time to time are merely the
> product of a deranged imagination." - Douglas Adams
>
>
>
> SHAW,JIANN-DER (A-Taiwan,ex1) wrote:
>> Hi Kevin,
>>
>> Just simply remove "do" object and un-check the clear file in dataset
>> object.
>> Please check if this is what you expected?
>>
>>
>> Best regards, Jiann-Der Shaw Application Engineering Organization
>> Agilent Technologies IDD: 886-3-4959344 Telnet: 846-3344 Mobile:
>> 886-917672043 (0917672043 in Taiwan)
>>
>>
>>
>> -----Original Message-----
>> From: Kevin Nievaart [mailto:Kevin.Nievaart@eng.monash.edu.au] Sent:
>> Wednesday, June 25, 2008 10:37 AM
>> To: PDL-LISTS,VRF (A-Lists,unix1)
>> Subject: [vrf] records and datasets
>>
>> G'day vrf'ers,
>> I'm having an issue with writing to and reading from datasets. I'd
>> like to be able to dynamically display an x vs y graph. The issue
>> is, I'd like to be able to read from the dataset while its being
>> written to. The idea is to be able to graph 1 field against time,
>> and mid test, be able to see the graph of a different field against
>> time. In order for this to work, I need to be able to:
>>
>> * write the latest data to the end of the dataset
>> * rewind the file
>> * read the entirety of the dataset
>> * repeat
>>
>> I'd like to do it like this as there are 30 fields I'd like to
>> potentially see.
>>
>> Nothing is working for me at the moment. In the attached vee file,
>> I've set up a simple 3 field dataset, and this program attempts to do
>> the above steps. However the green counter never gets above 6 before
>> the whole thing stops working. (the dataset output just constantly
>> out puts 0's for all 3 fields.) Any suggestions?
>> Cheers,
>>
>>
>
>
> ---
> You are currently subscribed to vrf as:
> kevin.nievaart@eng.monash.edu.au To subscribe please send an email to:
> "vrf-request@lists.it.agilent.com" with the word subscribe in the
> message body.
> To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com". If
> you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
>
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
That's not quite it, but it is quite clever.
I want to do this in real time. As data gets collected (in reality, this will be once every 5 seconds for about 30 minutes to an hour, and then after that once every 10 minutes for the next 6 months) I want to display the results (31 fields in all - 1 is time and the other 30 are
sensors) on an x vs y chart - x being time and y being any one of these sensors. I had in mind using a slider list to select which sensor I'm currently looking at.
As more data comes down, I'd like to be able to update the graph with the latest values while keeping the first values. This means that the sensors get read, data gets saved to a dataset file, and the entirety of the dataset file gets read to produce the graph. Next cycle, the sensors get read, data gets appended to the dataset file, and the entirety of the dataset gets read to produce the graph again. And so on and so on.
It is the saving to file, and then reading of the file that is killing me.
Is this clearer?
Unfortunately I can't really send on the actual program I'm working on, as it uses DDE to communicate with the data acquisition system (Datataker DT505) which won't work for the vast majority of you.
--
Kevin Nievaart
Materials Testing Officer
Dept. Civil Engineering
Monash University, Clayton Campus
Ph. (03) 9905-1165
Fax (03) 9905-1483
"It is known that there is an infinite number of worlds, simply because there is an infinite amount of space for them to be in. However, not every one of them is inhabited. Therefore, there must be a finite number of inhabited worlds. Any finite number divided by infinity is as near to nothing as makes no odds, so the average population of all the planets in the universe can be said to be zero. From this it follows that the population of the universe is also zero, and that any people you may meet from time to time are merely the product of a deranged imagination." - Douglas Adams
per.g.sorensen@nokia.com wrote:
> Hello Kevin.
>
> I attach an example program for you. I'm not sure, is this what you
> want to do?
>
> Br Per
>
>
>
>
>
>
>> -----Original Message-----
>> From: ext Kevin Nievaart [mailto:Kevin.Nievaart@eng.monash.edu.au]
>> Sent: Thursday, June 26, 2008 07:56
>> To: VRF
>> Subject: Re: [vrf] records and datasets
>>
>> Also, that vee file seems to be unstable - its crashed my VEE session
>> now on 8 seperate occasions - not sure whats causing that.
>> I'm using VEE 7.5 on a winxp sp2 box
>>
>> --
>> Kevin Nievaart
>> Materials Testing Officer
>>
>> Dept. Civil Engineering
>> Monash University, Clayton Campus
>> Ph. (03) 9905-1165
>> Fax (03) 9905-1483
>>
>>
>> "It is known that there is an infinite number of worlds, simply
>> because there is an infinite amount of space for them to be in.
>> However, not every one of them is inhabited.
>> Therefore, there must be a finite number of inhabited worlds.
>> Any finite number divided by infinity is as near to nothing as makes
>> no odds, so the average population of all the planets in the universe
>> can be said to be zero. From this it follows that the population of
>> the universe is also zero, and that any people you may meet from time
>> to time are merely the product
>> of a deranged imagination." - Douglas Adams
>>
>>
>>
>> Kevin Nievaart wrote:
>>
>>> G'day Jiann-Der,
>>> No that isn't what I'm after. The idea is that data gets collected
>>> into a dataset, the datafile gets rewound, and then ALL data
>>>
>> gets read
>>
>>> into an array of records - the do object is necessary here for this.
>>> Removing the do object (and the rewind pin) results in only the last
>>> data point being read. I also get an error if I uncheck the "clear
>>> file at pre-run" option.
>>>
>>> --
>>> Kevin Nievaart
>>> Materials Testing Officer
>>>
>>> Dept. Civil Engineering
>>> Monash University, Clayton Campus
>>> Ph. (03) 9905-1165
>>> Fax (03) 9905-1483
>>>
>>>
>>> "It is known that there is an infinite number of worlds, simply
>>> because there is an infinite amount of space for them to be in.
>>> However, not every one of them is inhabited. Therefore,
>>>
>> there must be
>>
>>> a finite number of inhabited worlds. Any finite number divided by
>>> infinity is as near to nothing as makes no odds, so the average
>>> population of all the planets in the universe can be said to be zero.
>>> From this it follows that the population of the universe is
>>>
>> also zero,
>>
>>> and that any people you may meet from time to time are merely the
>>> product of a deranged imagination." - Douglas Adams
>>>
>>>
>>>
>>> SHAW,JIANN-DER (A-Taiwan,ex1) wrote:
>>>
>>>> Hi Kevin,
>>>>
>>>> Just simply remove "do" object and un-check the clear file
>>>>
>> in dataset
>>
>>>> object.
>>>> Please check if this is what you expected?
>>>>
>>>>
>>>> Best regards, Jiann-Der Shaw Application Engineering Organization
>>>> Agilent Technologies IDD: 886-3-4959344 Telnet: 846-3344 Mobile:
>>>> 886-917672043 (0917672043 in Taiwan)
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Kevin Nievaart
>>>>
>> [mailto:Kevin.Nievaart@eng.monash.edu.au] Sent:
>>
>>>> Wednesday, June 25, 2008 10:37 AM
>>>> To: PDL-LISTS,VRF (A-Lists,unix1)
>>>> Subject: [vrf] records and datasets
>>>>
>>>> G'day vrf'ers,
>>>> I'm having an issue with writing to and reading from datasets. I'd
>>>> like to be able to dynamically display an x vs y graph. The issue
>>>> is, I'd like to be able to read from the dataset while its being
>>>> written to. The idea is to be able to graph 1 field against time,
>>>> and mid test, be able to see the graph of a different field against
>>>> time. In order for this to work, I need to be able to:
>>>>
>>>> * write the latest data to the end of the dataset
>>>> * rewind the file
>>>> * read the entirety of the dataset
>>>> * repeat
>>>>
>>>> I'd like to do it like this as there are 30 fields I'd like to
>>>> potentially see.
>>>>
>>>> Nothing is working for me at the moment. In the attached vee file,
>>>> I've set up a simple 3 field dataset, and this program
>>>>
>> attempts to do
>>
>>>> the above steps. However the green counter never gets
>>>>
>> above 6 before
>>
>>>> the whole thing stops working. (the dataset output just constantly
>>>> out puts 0's for all 3 fields.) Any suggestions?
>>>> Cheers,
>>>>
>>>>
>>>>
>>> ---
>>> You are currently subscribed to vrf as:
>>> kevin.nievaart@eng.monash.edu.au To subscribe please send an
>>>
>> email to:
>>
>>> "vrf-request@lists.it.agilent.com" with the word subscribe in the
>>> message body.
>>> To unsubscribe send a blank email to
>>>
>> "leave-vrf@it.lists.it.agilent.com".
>>
>>> To send messages to this mailing list, email "vrf@agilent.com". If
>>> you need help with the mailing list send a message to
>>> "owner-vrf@it.lists.it.agilent.com".
>>> Search the "unofficial vrf archive" at
>>> "http://www.vrfarchive.com/vrf_archive".
>>> Search the Agilent vrf archive at
>>>
>> "http://vee.engineering.agilent.com".
>>
>> ---
>> You are currently subscribed to vrf as:
>> per.g.sorensen@nokia.com To subscribe please send an email to:
>> "vrf-request@lists.it.agilent.com" with the word subscribe in the
>> message body.
>> To unsubscribe send a blank email to
>> "leave-vrf@it.lists.it.agilent.com".
>> To send messages to this mailing list, email "vrf@agilent.com".
>> If you need help with the mailing list send a message to
>> "owner-vrf@it.lists.it.agilent.com".
>> Search the "unofficial vrf archive" at
>> "http://www.vrfarchive.com/vrf_archive".
>> Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
>>
>>
> >
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
That's not quite it, but it is quite clever.
I want to do this in real time. As data gets collected (in reality, this will be once every 5 seconds for about 30 minutes to an hour, and then after that once every 10 minutes for the next 6 months) I want to display the results (31 fields in all - 1 is time and the other 30 are
sensors) on an x vs y chart - x being time and y being any one of these sensors. I had in mind using a slider list to select which sensor I'm currently looking at.
As more data comes down, I'd like to be able to update the graph with the latest values while keeping the first values. This means that the sensors get read, data gets saved to a dataset file, and the entirety of the dataset file gets read to produce the graph. Next cycle, the sensors get read, data gets appended to the dataset file, and the entirety of the dataset gets read to produce the graph again. And so on and so on.
It is the saving to file, and then reading of the file that is killing me.
Is this clearer?
Unfortunately I can't really send on the actual program I'm working on, as it uses DDE to communicate with the data acquisition system (Datataker DT505) which won't work for the vast majority of you.
--
Kevin Nievaart
Materials Testing Officer
Dept. Civil Engineering
Monash University, Clayton Campus
Ph. (03) 9905-1165
Fax (03) 9905-1483
"It is known that there is an infinite number of worlds, simply because there is an infinite amount of space for them to be in. However, not every one of them is inhabited. Therefore, there must be a finite number of inhabited worlds. Any finite number divided by infinity is as near to nothing as makes no odds, so the average population of all the planets in the universe can be said to be zero. From this it follows that the population of the universe is also zero, and that any people you may meet from time to time are merely the product of a deranged imagination." - Douglas Adams
per.g.sorensen@nokia.com wrote:
> Hello Kevin.
>
> I attach an example program for you. I'm not sure, is this what you
> want to do?
>
> Br Per
>
>
>
>
>
>
>> -----Original Message-----
>> From: ext Kevin Nievaart [mailto:Kevin.Nievaart@eng.monash.edu.au]
>> Sent: Thursday, June 26, 2008 07:56
>> To: VRF
>> Subject: Re: [vrf] records and datasets
>>
>> Also, that vee file seems to be unstable - its crashed my VEE session
>> now on 8 seperate occasions - not sure whats causing that.
>> I'm using VEE 7.5 on a winxp sp2 box
>>
>> --
>> Kevin Nievaart
>> Materials Testing Officer
>>
>> Dept. Civil Engineering
>> Monash University, Clayton Campus
>> Ph. (03) 9905-1165
>> Fax (03) 9905-1483
>>
>>
>> "It is known that there is an infinite number of worlds, simply
>> because there is an infinite amount of space for them to be in.
>> However, not every one of them is inhabited.
>> Therefore, there must be a finite number of inhabited worlds.
>> Any finite number divided by infinity is as near to nothing as makes
>> no odds, so the average population of all the planets in the universe
>> can be said to be zero. From this it follows that the population of
>> the universe is also zero, and that any people you may meet from time
>> to time are merely the product
>> of a deranged imagination." - Douglas Adams
>>
>>
>>
>> Kevin Nievaart wrote:
>>
>>> G'day Jiann-Der,
>>> No that isn't what I'm after. The idea is that data gets collected
>>> into a dataset, the datafile gets rewound, and then ALL data
>>>
>> gets read
>>
>>> into an array of records - the do object is necessary here for this.
>>> Removing the do object (and the rewind pin) results in only the last
>>> data point being read. I also get an error if I uncheck the "clear
>>> file at pre-run" option.
>>>
>>> --
>>> Kevin Nievaart
>>> Materials Testing Officer
>>>
>>> Dept. Civil Engineering
>>> Monash University, Clayton Campus
>>> Ph. (03) 9905-1165
>>> Fax (03) 9905-1483
>>>
>>>
>>> "It is known that there is an infinite number of worlds, simply
>>> because there is an infinite amount of space for them to be in.
>>> However, not every one of them is inhabited. Therefore,
>>>
>> there must be
>>
>>> a finite number of inhabited worlds. Any finite number divided by
>>> infinity is as near to nothing as makes no odds, so the average
>>> population of all the planets in the universe can be said to be zero.
>>> From this it follows that the population of the universe is
>>>
>> also zero,
>>
>>> and that any people you may meet from time to time are merely the
>>> product of a deranged imagination." - Douglas Adams
>>>
>>>
>>>
>>> SHAW,JIANN-DER (A-Taiwan,ex1) wrote:
>>>
>>>> Hi Kevin,
>>>>
>>>> Just simply remove "do" object and un-check the clear file
>>>>
>> in dataset
>>
>>>> object.
>>>> Please check if this is what you expected?
>>>>
>>>>
>>>> Best regards, Jiann-Der Shaw Application Engineering Organization
>>>> Agilent Technologies IDD: 886-3-4959344 Telnet: 846-3344 Mobile:
>>>> 886-917672043 (0917672043 in Taiwan)
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Kevin Nievaart
>>>>
>> [mailto:Kevin.Nievaart@eng.monash.edu.au] Sent:
>>
>>>> Wednesday, June 25, 2008 10:37 AM
>>>> To: PDL-LISTS,VRF (A-Lists,unix1)
>>>> Subject: [vrf] records and datasets
>>>>
>>>> G'day vrf'ers,
>>>> I'm having an issue with writing to and reading from datasets. I'd
>>>> like to be able to dynamically display an x vs y graph. The issue
>>>> is, I'd like to be able to read from the dataset while its being
>>>> written to. The idea is to be able to graph 1 field against time,
>>>> and mid test, be able to see the graph of a different field against
>>>> time. In order for this to work, I need to be able to:
>>>>
>>>> * write the latest data to the end of the dataset
>>>> * rewind the file
>>>> * read the entirety of the dataset
>>>> * repeat
>>>>
>>>> I'd like to do it like this as there are 30 fields I'd like to
>>>> potentially see.
>>>>
>>>> Nothing is working for me at the moment. In the attached vee file,
>>>> I've set up a simple 3 field dataset, and this program
>>>>
>> attempts to do
>>
>>>> the above steps. However the green counter never gets
>>>>
>> above 6 before
>>
>>>> the whole thing stops working. (the dataset output just constantly
>>>> out puts 0's for all 3 fields.) Any suggestions?
>>>> Cheers,
>>>>
>>>>
>>>>
>>> ---
>>> You are currently subscribed to vrf as:
>>> kevin.nievaart@eng.monash.edu.au To subscribe please send an
>>>
>> email to:
>>
>>> "vrf-request@lists.it.agilent.com" with the word subscribe in the
>>> message body.
>>> To unsubscribe send a blank email to
>>>
>> "leave-vrf@it.lists.it.agilent.com".
>>
>>> To send messages to this mailing list, email "vrf@agilent.com". If
>>> you need help with the mailing list send a message to
>>> "owner-vrf@it.lists.it.agilent.com".
>>> Search the "unofficial vrf archive" at
>>> "http://www.vrfarchive.com/vrf_archive".
>>> Search the Agilent vrf archive at
>>>
>> "http://vee.engineering.agilent.com".
>>
>> ---
>> You are currently subscribed to vrf as:
>> per.g.sorensen@nokia.com To subscribe please send an email to:
>> "vrf-request@lists.it.agilent.com" with the word subscribe in the
>> message body.
>> To unsubscribe send a blank email to
>> "leave-vrf@it.lists.it.agilent.com".
>> To send messages to this mailing list, email "vrf@agilent.com".
>> If you need help with the mailing list send a message to
>> "owner-vrf@it.lists.it.agilent.com".
>> Search the "unofficial vrf archive" at
>> "http://www.vrfarchive.com/vrf_archive".
>> Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
>>
>>
> >
---
You are currently subscribed to vrf as: hua_jing@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Basically, I see two problems. One is synchronization. You've got two threads trying to access the same file. VEE uses one file pointer for each unique file. IOW, there's only one file pointer for both files, so when the threads go out of sync something is going to break.
Second is "clear file at open". Every time this file is opened it's cleared.
Certainly not what you want.
What you need IMO is a client/server architecture. The server collects data & writes it to an accumulator file and the client reads & displays data.
Two separate programs. Two separate file pointers.
Unfortunately, you can't use sharing so file access has to be guarded. In VEE terms, it's probably simplest to put an error output on the file access objects & simply delay for a short period when you get a sharing violation.
If you expect this to run for a long time error pins can be a problem. When I ran across this I got roughly 300,000 error pings before VEE lost it's cookies.
If you want to use API functionality directly, you could easily do the whole thing in one program but then you wouldn't be able to use datasets, so that might be more trouble than it's worth.
-SHAWN-
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Basically, I see two problems. One is synchronization. You've got two threads trying to access the same file. VEE uses one file pointer for each unique file. IOW, there's only one file pointer for both files, so when the threads go out of sync something is going to break.
Second is "clear file at open". Every time this file is opened it's cleared.
Certainly not what you want.
What you need IMO is a client/server architecture. The server collects data & writes it to an accumulator file and the client reads & displays data.
Two separate programs. Two separate file pointers.
Unfortunately, you can't use sharing so file access has to be guarded. In VEE terms, it's probably simplest to put an error output on the file access objects & simply delay for a short period when you get a sharing violation.
If you expect this to run for a long time error pins can be a problem. When I ran across this I got roughly 300,000 error pings before VEE lost it's cookies.
If you want to use API functionality directly, you could easily do the whole thing in one program but then you wouldn't be able to use datasets, so that might be more trouble than it's worth.
-SHAWN-
---
You are currently subscribed to vrf as: hua_jing@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
I'm not sure what you guys are trying to do, but it looks like someone needs to use a data base with multiple accesses.
Rufus
-----Original Message-----
From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
Sent: Friday, June 27, 2008 4:14 PM
To: VRF
Subject: RE: [vrf] records and datasets
I don't think this is going to get you there.
Basically, I see two problems. One is synchronization. You've got two threads trying to access the same file. VEE uses one file pointer for each unique file. IOW, there's only one file pointer for both files, so when the threads go out of sync something is going to break.
Second is "clear file at open". Every time this file is opened it's cleared.
Certainly not what you want.
What you need IMO is a client/server architecture. The server collects data & writes it to an accumulator file and the client reads & displays data.
Two separate programs. Two separate file pointers.
Unfortunately, you can't use sharing so file access has to be guarded.
In
VEE terms, it's probably simplest to put an error output on the file access objects & simply delay for a short period when you get a sharing violation.
If you expect this to run for a long time error pins can be a problem.
When
I ran across this I got roughly 300,000 error pings before VEE lost it's cookies.
If you want to use API functionality directly, you could easily do the whole thing in one program but then you wouldn't be able to use datasets, so that might be more trouble than it's worth.
-SHAWN-
---
You are currently subscribed to vrf as: Rufus.Warren@herley.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com"
with the word subscribe in the message body.
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at
"http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
The information contained in this message may be confidential and legally privileged. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in error.
---
You are currently subscribed to vrf as: hua_jing@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
I'm not sure what you guys are trying to do, but it looks like someone needs to use a data base with multiple accesses.
Rufus
-----Original Message-----
From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
Sent: Friday, June 27, 2008 4:14 PM
To: VRF
Subject: RE: [vrf] records and datasets
I don't think this is going to get you there.
Basically, I see two problems. One is synchronization. You've got two threads trying to access the same file. VEE uses one file pointer for each unique file. IOW, there's only one file pointer for both files, so when the threads go out of sync something is going to break.
Second is "clear file at open". Every time this file is opened it's cleared.
Certainly not what you want.
What you need IMO is a client/server architecture. The server collects data & writes it to an accumulator file and the client reads & displays data.
Two separate programs. Two separate file pointers.
Unfortunately, you can't use sharing so file access has to be guarded.
In
VEE terms, it's probably simplest to put an error output on the file access objects & simply delay for a short period when you get a sharing violation.
If you expect this to run for a long time error pins can be a problem.
When
I ran across this I got roughly 300,000 error pings before VEE lost it's cookies.
If you want to use API functionality directly, you could easily do the whole thing in one program but then you wouldn't be able to use datasets, so that might be more trouble than it's worth.
-SHAWN-
---
You are currently subscribed to vrf as: Rufus.Warren@herley.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com"
with the word subscribe in the message body.
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at
"http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
The information contained in this message may be confidential and legally privileged. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in error.
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Then again, sometimes a minimalist approach is enough of a demo to get the check
My my. Three years ago I would have said, "...after there's bread on the table."
-SHAWN-
> -----Original Message-----
> From: Warren, Rufus [mailto:Rufus.Warren@Herley.Com]
> Sent: Friday, June 27, 2008 3:23 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
>
> Shawn,
>
> I'm not sure what you guys are trying to do, but it looks like someone
> needs to use a data base with multiple accesses.
>
> Rufus
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
> Sent: Friday, June 27, 2008 4:14 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
> I don't think this is going to get you there.
>
> Basically, I see two problems. One is synchronization. You've got two
> threads trying to access the same file. VEE uses one file pointer for
> each unique file. IOW, there's only one file pointer for both files,
> so when the threads go out of sync something is going to break.
>
> Second is "clear file at open". Every time this file is opened it's
> cleared.
> Certainly not what you want.
>
> What you need IMO is a client/server architecture. The server collects
> data & writes it to an accumulator file and the client reads &
> displays data.
> Two separate programs. Two separate file pointers.
>
> Unfortunately, you can't use sharing so file access has to be guarded.
> In
> VEE terms, it's probably simplest to put an error output on the file
> access objects & simply delay for a short period when you get a
> sharing violation.
>
> If you expect this to run for a long time error pins can be a problem.
> When
> I ran across this I got roughly 300,000 error pings before VEE lost
> it's cookies.
>
> If you want to use API functionality directly, you could easily do the
> whole thing in one program but then you wouldn't be able to use
> datasets, so that might be more trouble than it's worth.
> -SHAWN-
>
>
>
>
> ---
> You are currently subscribed to vrf as: Rufus.Warren@herley.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com"
> with the word subscribe in the message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>
>
> The information contained in this message may be confidential and
> legally privileged. If you are not the intended recipient of this
> email and its attachments, you must take no action based upon them,
> nor must you copy or show them to anyone.
> Please contact the sender if you believe you have received this email
> in error.
>
>
>
>
>
> ---
> You are currently subscribed to vrf as: shawn@vrfarchive.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com" with the word subscribe in the
> message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>