Parallel instances using ONE Action Engine

Question

Hi Everyone.
I just wanted to see what type of ideas this would bring to this issue.
I have an AE that holds all the pointers (or referances) that 20 instances of a reentrantVI use in parallel. Obviously the issue is the execution speed as all the instances are waiting to read the AE (and probably a heap of other issues I haven't ecountered yet). 
I have placed an example of the AE that I am using where I also show HOW I'm using it on a bigger picture.
Please DO NOT RUN the example, just open it and see the BD, it is where I tried to put all the information on and it was the best way that I can think of to explain the issue.
Kas
Solved!
Go to Solution.
Attachments:
Example.zip ‏63 KB

Answer 1

johnsold wrote:
1. Are items 1 and 2 in Example.vi or the image guaranteed to run before 3 and 4 start? Or, can segments be added while the proceesing is occurring?
2. How do the changes made by item 4 affect the data not yet processed by item 3?  How do they affect segments already processed?
3. The only value on FGV.vi Segment: Out which is meaningful is the last one. The compiler is probably smart enough to not update it on earlier iterations but there might be a small speed improvement to moving the terminal outside the for loop.
4. When are the Get Segments and Get Items commands used?
5. Could a parallelized for loop do what you want rather than multiple reentrant VIs?
Ok, sorry for not properly explaining things. My explanation of My problem made sence in my head so I thought every one else will get it .
1. Items 1 and 2 are sequential, so guaranteed to run before 3 and 4. However, when 3 (the reentrant) is executed and sudenly gets an error (i.e. TCP TimeOut 56) then the segment function that was initialy changed to "in process" when taken out (before the timeout happened) is set again to "waiting" so that untill the error gets sorted, another reentrant can get the segment and does something with it. Also, if the reentrant in step 3 is executed and there are no errors then the output data is sent to item 4, which sets the function of the segment in AE to either "Damaged" or "Missing". This is happening while all the other reentrant VIs (in item 3) are still running.
2. Item 4 will ONLY make changes to the function of the segment AFTER item 3 has done something to it, and not before. And NO, after step 2 on my description, no Segments can be ADDED or DELETED. Only the segment Function changes. Based on this function, the segment is read. So, if the function says "waiting" then the data is sent out, otherwise, the reentrant VI thinks that all the segments are processed and so it exits (I do this through a "5003" error inside the AE). 
3. Ummm.. Maybe the compiler does what you say it does (no idea here) but I doubt it will give me any improvement that would make a difference to me.
4. They are used in my step 3 "Get segment" used ONCE (If no error) and TWICE (if error), "Get Items" used ONCE (if no error).
5. Won't make a difference, since the "Choke Point" is the AE. How you launch the VI won't make a difference. 
Kas