LAVA Forums Buy cool LAVA gear Forums RSS Feed

Welcome Guest ( Log In | Register )

Tags
This content has not been tagged yet

> Bug reporting guidelines:

See here for the proper LabVIEW bug reporting procedure.


 
Reply to this topic Start new topic
> "Wait for All Notifications" should be reentrant, Status: Filed with R&D (CAR#45BGR0J1)
Jim Kring
post Jan 12 2007, 11:04 PM
Post #1


Changing the world, one VI at a time.
*****

Premium Member
Posts: 1648
Joined: 22-October 02
From: San Francisco, CA
Member No.: 17
Using LabVIEW Since:1995
LV:8.2.1 ,8.5 ,7.1.1
United States us_california Nothing Selected My Blog My Gallery


[CAR 45BGR0J1]
The following VIs should obviously be reentrant (but they are not), in order for two parallel calls to work as expected:

\vi.lib\utility\Wait for All Notifcations.llb\Wait for All Notifications Sub.vi
\vi.lib\Utility\Wait for All Notifcations.llb\Wait for All Notifications.vi

--------------------
-----------------------------------------------------------------------------------------------------
| Book | OpenG | LAVA | Champion | VIPM | Builder | Blog | JKI |
-----------------------------------------------------------------------------------------------------


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
Ad
post Jan 12 2007, 11:04 PM
Post #















Tags
This content has not been tagged yet
Go to the top of the page
Quote Post
Aristos Queue
post Jan 12 2007, 11:51 PM
Post #2


LV R&D Envoy
*****

NI
Posts: 1143
Joined: 15-August 06
From: Austin, TX
Member No.: 5877
Using LabVIEW Since:2000
LV:8.5.1 ,. ,.
United States Nothing Selected Nothing Selected My Gallery


This was reported to R&D (#45BGR0J1) for further investigation. It will be fixed in the next full release of LV.

--------------------
"A VI outside a class is a gun without a safety. Data outside a class is a target."
--- A message from LabVOOP R&D


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
i2dx
post Jan 13 2007, 07:42 AM
Post #3


(n0ob)˛
****

Member
Posts: 756
Joined: 22-October 04
From: Duesseldorf / Germany
Member No.: 885
Using LabVIEW Since:2001
LV:8.20 ,7.1.1 ,.
ger_bavaria Germany ger_rhineland


QUOTE (Aristos Queue @ Jan 13 2007, 12:51 AM) *
This was reported to R&D (#45BGR0J1) for further investigation. It will be fixed in the next full release of LV.


It's nice to have a "non official but obviously fast and reliable mechanism with semi direct access to the developers for bug reporting" here smile.gif

Thank you Stephen smile.gif

--------------------
don't take me to serious
my Website my ADO-Toolkit for LabVIEW™


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
Aristos Queue
post Jan 15 2007, 01:57 AM
Post #4


LV R&D Envoy
*****

NI
Posts: 1143
Joined: 15-August 06
From: Austin, TX
Member No.: 5877
Using LabVIEW Since:2000
LV:8.5.1 ,. ,.
United States Nothing Selected Nothing Selected My Gallery


Kring has posted a tidal wave of bugs against this VI.
http://forums.lavag.org/Wait-for-All-Notifications-should-be-reentrant-t5780.html
http://forums.lavag.org/Wait-on-Notification-from-Multiple-output-notifier-values-are-wrong-on-error-t5807.html
http://forums.lavag.org/Wait-for-All-Notifications-outputs-extra-null-notification-t5804.html
http://forums.lavag.org/Wait-on-Notification-from-Multiple-output-values-can-be-wrong-on-timeout-t5802.html
I'll ask the original author of the VI to take a long hard look at it and see if the example can be improved. I do own the Notifier primitives, but this particular example was written by someone else -- I asked that it be included in the shipping LabVIEW because the functionality gets asked for from time to time.

This post has been edited by Aristos Queue: Jan 15 2007, 02:02 AM

--------------------
"A VI outside a class is a gun without a safety. Data outside a class is a target."
--- A message from LabVOOP R&D


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
Jim Kring
post Jan 15 2007, 03:19 AM
Post #5


Changing the world, one VI at a time.
*****

Premium Member
Posts: 1648
Joined: 22-October 02
From: San Francisco, CA
Member No.: 17
Using LabVIEW Since:1995
LV:8.2.1 ,8.5 ,7.1.1
United States us_california Nothing Selected My Blog My Gallery


QUOTE (Aristos Queue @ Jan 14 2007, 05:57 PM) *
I'll ask the original author of the VI to take a long hard look at it and see if the example can be improved. I do own the Notifier primitives, but this particular example was written by someone else -- I asked that it be included in the shipping LabVIEW because the functionality gets asked for from time to time.


Stephen,

Thanks for pushing things forward on your side. One more thing... the description of the "notifiers out" indicator (which is shown in the context menu when you hover over the indicator) states: "notifiers out is the entire array of notifiers in, unless an error occurs. If an error occurs, notifiers out contains only those notifier refnums that caused the error." However, this is not the actual (or the desired, IMO) behavior. If some notifiers are received before the error occurs (for example, if one notifier becomes invalid after others are received), then the notifiers and notifications received should be output to "notifiers out" and "notifications" (respectively). I don't think that it is entirely possible to know which notifiers caused the error, since the "Wait on Notification from Multiple" primitive does not tell you which notifier generated the error. We could infer which notifiers caused the error by checking if any of them are Not a Refnum. But, in any case, the user of this VI could make this check, themselves, if an error did occur. If this VI does actually need to output an array of notifiers that caused the error, then I would prefer if this were an additional output ("notifiers with errors") and we used "notifiers out" to contain the notifiers that were actually fired.

Thanks a million!

--------------------
-----------------------------------------------------------------------------------------------------
| Book | OpenG | LAVA | Champion | VIPM | Builder | Blog | JKI |
-----------------------------------------------------------------------------------------------------


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
Aristos Queue
post Aug 1 2008, 09:00 PM
Post #6


LV R&D Envoy
*****

NI
Posts: 1143
Joined: 15-August 06
From: Austin, TX
Member No.: 5877
Using LabVIEW Since:2000
LV:8.5.1 ,. ,.
United States Nothing Selected Nothing Selected My Gallery


All these bugs were fixed in LV8.5.

--------------------
"A VI outside a class is a gun without a safety. Data outside a class is a target."
--- A message from LabVOOP R&D


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post

Collapse

> Similar Topics

    Topic Title Replies Topic Starter Views Last Action
No new   49 Jim Kring 16013 29th July 2008 - 03:51 AM
Last post by: Aristos Queue
No New Posts   0 JackHamilton 2734 10th January 2004 - 03:44 AM
Last post by: JackHamilton
No New Posts   0 Michael_Aivaliotis 1662 18th February 2004 - 03:10 AM
Last post by: Michael_Aivaliotis
No New Posts   4 didierj 2040 9th March 2004 - 06:44 AM
Last post by: didierj


Reply to this topicStart new topic

 




Time is now: 29th August 2008 - 06:08 PM