My organization recently updated IADS to vs 7.2. We are noticing an
issue when asking the software to automatically add markers at FES
start. The markers are created, but they do not show up in the event
marker log on their own. We have to scroll back, grab the visual
marker, and nudge it a little bit. An event will then show up in the
event marker log.
-----Original Message----- From: iads@googlegroups.com [mailto:iads@googlegroups.com] On Behalf Of Amy
Henderson Sent: Wednesday, November 16, 2011 10:41 AM To: IADS Subject: [IADS] Adding Event Markers at FES Start with IADS 7.2
My organization recently updated IADS to vs 7.2. We are noticing an issue when asking the software to automatically add markers at FES start. The markers are created, but they do not show up in the event marker log on their own. We have to scroll back, grab the visual marker, and nudge it a little bit. An event will then show up in the event marker log.
Anyone else notice this or have a solution?
-- You received this message because you are subscribed to the Google Groups "IADS" group. To post to this group, send email to iads@googlegroups.com. To unsubscribe from this group, send email to iads+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/iads?hl=en.
Amy, Sorry I accidently submitted the email before my train of thought was complete.
Also verify that the "Add event Marker at FES Start" is checked on the right click menu in the FES section of the dashboard.
Then verify the configuration of the Log Filter to make sure that it is not excluding you from seeing it. See how that goes and update us.. also if possible you can send the zipped Logs directory to iadssupport (at) symvionics.com.
Adam Chant Symvionics, Inc. IADS Application Engineer (661) 273-7003 x 210
-----Original Message----- From: iads@googlegroups.com [mailto:iads@googlegroups.com] On Behalf Of Amy
Henderson Sent: Wednesday, November 16, 2011 10:41 AM To: IADS Subject: [IADS] Adding Event Markers at FES Start with IADS 7.2
My organization recently updated IADS to vs 7.2. We are noticing an issue when asking the software to automatically add markers at FES start. The markers are created, but they do not show up in the event marker log on their own. We have to scroll back, grab the visual marker, and nudge it a little bit. An event will then show up in the event marker log.
Anyone else notice this or have a solution?
-- You received this message because you are subscribed to the Google Groups "IADS" group. To post to this group, send email to iads@googlegroups.com. To unsubscribe from this group, send email to iads+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/iads?hl=en.
AutoSave is enabled, as is "Add Event Marker at FES Start". Log
Filter is fine. We have used this functionality for quite a long time
with previous versions of IADS. It just seems strange that we now
have to move the visual marker before it will show up in the log.
Amy, I'm sorry, but it sounds like it may be some sort of bug. I have not yet reproduced it, but as you describe it that should not be the way it functions. We will continue to look into this and see if we can quickly find a solution.
Adam Chant Symvionics, Inc. IADS Application Engineer (661) 273-7003 x 210
-----Original Message----- From: iads@googlegroups.com [mailto:iads@googlegroups.com] On Behalf Of Amy
Henderson Sent: Thursday, November 17, 2011 8:10 AM To: IADS Subject: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
AutoSave is enabled, as is "Add Event Marker at FES Start". Log Filter is fine. We have used this functionality for quite a long time with previous versions of IADS. It just seems strange that we now have to move the visual marker before it will show up in the log.
I don't think I will be able to send anything.
Amy
-- You received this message because you are subscribed to the Google Groups "IADS" group. To post to this group, send email to iads@googlegroups.com. To unsubscribe from this group, send email to iads+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/iads?hl=en.
Everything here works as expected. If we check the box to add EventMarker at FES start, we get an event marker each time on both the stripchart and in the log.... in fact, there even if we set the view filter to exclude ourselves, it still appears in both locations. We can't get it to not show up (despite our attempts).
If you get a chance, try to make a backup of the original config file, delete all the event markers, and try to replicate this in post test. Instead of moving the EventMarker up and down, try moving around the scrollbar in the log. Also, try and inject your own event markers via the toolbar button on the AW and see it this behaves the same way.
Another question, do you have the log set to appear on top in the event of an update? In other words, does the log appear each time an event marker is added (even though you've minimized it)?
Is anyone else seeing this issue in your discipline? Jim
-------------------------------------------------- From: "Adam Chant" <a...@iads-soft.com> Sent: Thursday, November 17, 2011 8:27 AM To: <iads@googlegroups.com> Subject: RE: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
> Amy, > I'm sorry, but it sounds like it may be some sort of bug. I have not yet > reproduced it, but as you describe it that should not be the way it > functions. We will continue to look into this and see if we can quickly > find > a solution.
> Adam Chant > Symvionics, Inc. > IADS Application Engineer > (661) 273-7003 x 210
> -----Original Message----- > From: iads@googlegroups.com [mailto:iads@googlegroups.com] On Behalf Of > Amy > Henderson > Sent: Thursday, November 17, 2011 8:10 AM > To: IADS > Subject: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
> AutoSave is enabled, as is "Add Event Marker at FES Start". Log > Filter is fine. We have used this functionality for quite a long time > with previous versions of IADS. It just seems strange that we now > have to move the visual marker before it will show up in the log.
> I don't think I will be able to send anything.
> Amy
> -- > You received this message because you are subscribed to the Google Groups > "IADS" group. > To post to this group, send email to iads@googlegroups.com. > To unsubscribe from this group, send email to > iads+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/iads?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "IADS" group. > To post to this group, send email to iads@googlegroups.com. > To unsubscribe from this group, send email to > iads+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/iads?hl=en.
Functionality is as expected post test. Setting our own event markers works fine as well.
My site is the only one using vs 7.2 in my discipline. Another site recently updated to 7.2.1. They are not seeing this behavior. We will wait and see if this is resolved with a later version of IADS. Thank you for your help.
I can say with absolute certainty that nothing changed between 7.2 and 7.2.1 for event markers. In fact other then version numbers the only difference between those two is in the Operator's Console.
So, I would suspect that there are differences in how this is configured and/or being used between the two sites.
Would it be possible for you to send either the Logs directory or the configuration file to 'iadssupport (at) symvionics.com'<http://symvionics.com/> Please also provide any information you can about what username/desktop you are logging into and what Analysis Window/s you have visible. <http://symvionics.com/>
I am at the other site that Amy referred to. When we upgraded to IADS
7.2.1 in November, the automated marker drops still worked. Since the
new year, the automated markers exhibit the same failure to work that
Amy described. In a post-test environment with version 7.2 at my
desk, the markers drop AND the Event Log is populated, so that works
fine. The only change between November and now is that there was an
issue in one flight with the IAP reconstruction of the FES signal not
working properly. Since they fixed that, the event markers do not
make it into the log automatically.
When the Event Log is not populated, I can go back on the screen and
wiggle the marker as Amy described, which puts the entry in the event
log. But, if there is a test point dropped at nearly the same time by
another discipline and I don't have it filtered out already, I have
trouble getting the event marker selected to move it. If I then go
and filter the test point markers out, the event markers that have not
yet made it into the log disappear.
This problem is a huge annoyance during a flutter mission. Are we
stuck waiting and hoping that something miraculously gets fixed in the
next version of IADS, or is the problem understood? Is there a better
workaround?
Sorry you're having problems. Let me try and understand the issue because it seems different that Amy's.
> I am at the other site that Amy referred to. When we upgraded to IADS > 7.2.1 in November, the automated marker drops still worked. Since the > new year, the automated markers exhibit the same failure to work that > Amy described. In a post-test environment with version 7.2 at my > desk, the markers drop AND the Event Log is populated, so that works > fine. The only change between November and now is that there was an > issue in one flight with the IAP reconstruction of the FES signal not > working properly. Since they fixed that, the event markers do not > make it into the log automatically.
From what I gather, you're referring to the "EventMarkers", correct? Amy was referring to the "Test Point" markers (two different marking systems). I just want to make sure we're on the same track here.
And when you say "do not make it into the log automatically", do you mean that you set up the system to automatically (without user intervention) create an event marker? Or do you mean that a user clicks on the EventMarker (or TestPoint) to create and nothing appears in the logs (but appears on the StripChart.
The FES reconstruction shouldn't have had any baring on this problem. The FES reconstruction is simply a derived parameter in the system...... but, if you're talking about "create an Event Marker on FES start" then maybe there is some correlation. Is that what you're referring to?
> When the Event Log is not populated, I can go back on the screen and > wiggle the marker as Amy described, which puts the entry in the event > log.
Well, this is slightly different than what Amy described (if I remember correctly). She says that the entry (test point not event marker) is visible in both the StripChart and the log until she wiggles it.... at which point it disappears from the log but stays on the stripchart. Sounds like you're seeing the exact opposite (but equally as annoying) behavior. Her workaround was to not "wiggle" the marker but edit the start/stop time in the log directly. This seems to mask the problem.
In either case we tried for several days to duplicate this problem (with your configuration files) and reviewed all the code. We just couldn't track it down. Any clue as to how to reproduce this behavior would appreciated. If we could reproduce it then we'd fix it right away... but we just don't see it or any clue of it happening in the code (although it's obviously happening somehow).
> But, if there is a test point dropped at nearly the same time by > another discipline and I don't have it filtered out already, I have > trouble getting the event marker selected to move it. If I then go > and filter the test point markers out, the event markers that have not > yet made it into the log disappear.
Hmmmm... I have read that section 4 times and I don't quite understand. You're using the term "event marker" and "test point". Iads has both EventMarkers and TestPoints. Are you referring to both or just one?
"the event markers that have not yet made it into the the log disappear"... Hmmm. Are you saying that you see event markers on your StripChart that are not in the log and then they suddenly are removed from the stipchart?
A marker (either TestPoint or EventMarker) should be both on the StripChart and in the logs simultaneously... in fact, both of those items are reading from the internal "database". If one or the other is not present then we have some crazy bug to track down. This is the first time we've heard of such a problem so it must have crept in on version 7.X.
> This problem is a huge annoyance during a flutter mission. Are we > stuck waiting and hoping that something miraculously gets fixed in the > next version of IADS, or is the problem understood? Is there a better > workaround?
Sorry for the problems. Honestly. we would fix it right now and have a "patch" out to your facility if we could just pinpoint the problem. Any help reproducing it would be highly appreciated.
Can you tell us the *exact* steps that go into creating the markers (Event or TestPoint) and what exactly sets off the problem?
The workarounds so far seem to be: 1) Don't modify the Marker position in the mission (do it in post test). User confirmed the problem doesn't exist in post test 2) If you need to modify the times of the marker, do so by editing the associated log entry (not by moving the marker with your cursor).
Again, sorry for these problems but we just don't see these issues happening.
Question: Are these issues happening at the other sites?? Can you ask around? Maybe it's related to a configuration issue somehow.
Also keep in mind that many of these settings are tied to the username at login time. Is there any possibility that you are using a different username in PostTest vs Realtime? This might explain why it works in one mode and not the othe
It seems that wires got crossed somewhere. Refer to Amy's first post
where she says she DID have to move the event marker to get it to show
up in the log. We are using the exact same methods and having the
same issues. And for Michael Jones, I was using the exact same login
real time and post test.
Let me try to describe the problem in excruciating detail so that it
is clear. When using FES to excite a mode in a flutter mission, we
want a marker to automatically be dropped at the FES start. To do so,
we turn on the Automated Analysis button on the dashboard so that it
reads "Automated Analysis Enabled". We also right-click above that
button and check "Add Event Marker at FES Start". There is no option
to automatically drop Test Point Markers at FES start and stop, so we
DO NOT use Test Point Markers.
With the "Automated Analysis Enabled" and "Add Event Marker at FES
Start" checked, up until IADS 7.2 we would have both an event marker
dropped on the displays AND the event entry added to the Event Markers
tab in the IADS Logs at the start of the FES event. The Log entry
doesn't show up until the FES event is complete, but it is there.
Once we updated to version 7.2 of IADS, using the setup of "Automated
Analysis Enabled" and "Add Event Marker at FES Start" still drops the
Event Marker, but no entry is placed in the Event Marker tab of the
IADS Logs. To get the entry in the Event Marker tab of the IADS Logs,
you have to return to the displays and nudge the Event Marker (the
green line) slightly.
If another discipline is using Test Point Markers or Event Markers
that get dropped at the same time, it is difficult to pick the FES
Event Marker from the 2+ overlaying markers. One time, I did not have
the Test Point Marker filters set up in the IADS Logs ahead of time to
filter out the Test Point Markers from other disciplines. When I
filtered the Test Point Markers after the FES event was complete so
that I could isolate the FES Test Point Marker to be able to nudge it,
the FES Test Point Marker disappeared completely. Those markers that
I had previously nudged (for earlier FES bursts) that had already made
it into the Event Marker tab of the IADS Logs, did not disappear.
I hope that clarifies the problem we are seeing. However, we
discovered another "feature" of this bug in yesterday's mission that
explains why we did not see the problem until now. When the IADS Logs
window is VISIBLE on the screen during the FES event, the Event Marker
for the FES event is automatically dropped on the display AND the
entry makes it into the Event Markers tab of the IADS Log. Because of
real estate constraints, we usually run with the IADS Logs window
minimized (not closed). When the IADS Logs window is minimized, the
Event Marker for the FES event is automatically dropped on the display
BUT the entry does not show up in the Event Markers tab of the IADS
Logs. Late last year, after we had upgraded to IADS 7.2, the engineer
who was the keeper of the Logs always had the IADS Logs window
visible, so we did not think we had the issue with the FES events
automatically making it into the Logs. We saw the issue this year
when I became the "stuckee" who was responsible for keeping the Log
and I had the IADS Logs window minimized.
However, in a post-test environment, the FES entries automatically
make it into the Event Marker tab of the IADS Logs regardless of
whether the IADS Logs window is visible or minimized. So, to
replicate the problem, it appears you have to do it in a real time
environment with the IADS Logs window minimized.
At least we have found a less distracting work-around for now.
Actually, it was my wires that got crossed. TJ from the FQ group reported the other problem and I got it mixed up with Amy's post.
Thank you for the excellent description. I'll try to replicate this issue again. Sounds like you already cornered the problem (minimized log issue perhaps).
I'll get back to you ASAP, Jim
-------------------------------------------------- From: "David D" <david.k.d...@lmco.com> Sent: Thursday, January 19, 2012 9:54 AM To: "IADS" <iads@googlegroups.com> Subject: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
> It seems that wires got crossed somewhere. Refer to Amy's first post > where she says she DID have to move the event marker to get it to show > up in the log. We are using the exact same methods and having the > same issues. And for Michael Jones, I was using the exact same login > real time and post test.
> Let me try to describe the problem in excruciating detail so that it > is clear. When using FES to excite a mode in a flutter mission, we > want a marker to automatically be dropped at the FES start. To do so, > we turn on the Automated Analysis button on the dashboard so that it > reads "Automated Analysis Enabled". We also right-click above that > button and check "Add Event Marker at FES Start". There is no option > to automatically drop Test Point Markers at FES start and stop, so we > DO NOT use Test Point Markers.
> With the "Automated Analysis Enabled" and "Add Event Marker at FES > Start" checked, up until IADS 7.2 we would have both an event marker > dropped on the displays AND the event entry added to the Event Markers > tab in the IADS Logs at the start of the FES event. The Log entry > doesn't show up until the FES event is complete, but it is there. > Once we updated to version 7.2 of IADS, using the setup of "Automated > Analysis Enabled" and "Add Event Marker at FES Start" still drops the > Event Marker, but no entry is placed in the Event Marker tab of the > IADS Logs. To get the entry in the Event Marker tab of the IADS Logs, > you have to return to the displays and nudge the Event Marker (the > green line) slightly.
> If another discipline is using Test Point Markers or Event Markers > that get dropped at the same time, it is difficult to pick the FES > Event Marker from the 2+ overlaying markers. One time, I did not have > the Test Point Marker filters set up in the IADS Logs ahead of time to > filter out the Test Point Markers from other disciplines. When I > filtered the Test Point Markers after the FES event was complete so > that I could isolate the FES Test Point Marker to be able to nudge it, > the FES Test Point Marker disappeared completely. Those markers that > I had previously nudged (for earlier FES bursts) that had already made > it into the Event Marker tab of the IADS Logs, did not disappear.
> I hope that clarifies the problem we are seeing. However, we > discovered another "feature" of this bug in yesterday's mission that > explains why we did not see the problem until now. When the IADS Logs > window is VISIBLE on the screen during the FES event, the Event Marker > for the FES event is automatically dropped on the display AND the > entry makes it into the Event Markers tab of the IADS Log. Because of > real estate constraints, we usually run with the IADS Logs window > minimized (not closed). When the IADS Logs window is minimized, the > Event Marker for the FES event is automatically dropped on the display > BUT the entry does not show up in the Event Markers tab of the IADS > Logs. Late last year, after we had upgraded to IADS 7.2, the engineer > who was the keeper of the Logs always had the IADS Logs window > visible, so we did not think we had the issue with the FES events > automatically making it into the Logs. We saw the issue this year > when I became the "stuckee" who was responsible for keeping the Log > and I had the IADS Logs window minimized.
> However, in a post-test environment, the FES entries automatically > make it into the Event Marker tab of the IADS Logs regardless of > whether the IADS Logs window is visible or minimized. So, to > replicate the problem, it appears you have to do it in a real time > environment with the IADS Logs window minimized.
> At least we have found a less distracting work-around for now.
> -- > You received this message because you are subscribed to the Google Groups > "IADS" group. > To post to this group, send email to iads@googlegroups.com. > To unsubscribe from this group, send email to > iads+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/iads?hl=en.
Thanx to your help, I think we cornered the problem. Apparently this bug has been in Iads since the inception of "create EM at FES start" and nobody has ever reported it (until now).
The problem occurs when the auto analysis creates an EventMarker without the log being visible. If this occurs and an EventMarker is saved from another user, the log entry gets erased (which of course shouldn't be occurring).
We'll fix this soon and follow up with a patch.
The only workaround we can see right now is to leave the log visible (you can position it almost completely off the screen).... You could also manually create an Event Marker, but this would be more cumbersome.
Sorry for the problems, Jim
-------------------------------------------------- From: "James Bretz" <j...@iads-soft.com> Sent: Thursday, January 19, 2012 10:35 AM To: "IADS" <iads@googlegroups.com> Subject: Re: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
> Actually, it was my wires that got crossed. TJ from the FQ group reported > the other problem and I got it mixed up with Amy's post.
> Thank you for the excellent description. I'll try to replicate this issue > again. Sounds like you already cornered the problem (minimized log issue > perhaps).
> I'll get back to you ASAP, > Jim
> -------------------------------------------------- > From: "David D" <david.k.d...@lmco.com> > Sent: Thursday, January 19, 2012 9:54 AM > To: "IADS" <iads@googlegroups.com> > Subject: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
>> Jim,
>> It seems that wires got crossed somewhere. Refer to Amy's first post >> where she says she DID have to move the event marker to get it to show >> up in the log. We are using the exact same methods and having the >> same issues. And for Michael Jones, I was using the exact same login >> real time and post test.
>> Let me try to describe the problem in excruciating detail so that it >> is clear. When using FES to excite a mode in a flutter mission, we >> want a marker to automatically be dropped at the FES start. To do so, >> we turn on the Automated Analysis button on the dashboard so that it >> reads "Automated Analysis Enabled". We also right-click above that >> button and check "Add Event Marker at FES Start". There is no option >> to automatically drop Test Point Markers at FES start and stop, so we >> DO NOT use Test Point Markers.
>> With the "Automated Analysis Enabled" and "Add Event Marker at FES >> Start" checked, up until IADS 7.2 we would have both an event marker >> dropped on the displays AND the event entry added to the Event Markers >> tab in the IADS Logs at the start of the FES event. The Log entry >> doesn't show up until the FES event is complete, but it is there. >> Once we updated to version 7.2 of IADS, using the setup of "Automated >> Analysis Enabled" and "Add Event Marker at FES Start" still drops the >> Event Marker, but no entry is placed in the Event Marker tab of the >> IADS Logs. To get the entry in the Event Marker tab of the IADS Logs, >> you have to return to the displays and nudge the Event Marker (the >> green line) slightly.
>> If another discipline is using Test Point Markers or Event Markers >> that get dropped at the same time, it is difficult to pick the FES >> Event Marker from the 2+ overlaying markers. One time, I did not have >> the Test Point Marker filters set up in the IADS Logs ahead of time to >> filter out the Test Point Markers from other disciplines. When I >> filtered the Test Point Markers after the FES event was complete so >> that I could isolate the FES Test Point Marker to be able to nudge it, >> the FES Test Point Marker disappeared completely. Those markers that >> I had previously nudged (for earlier FES bursts) that had already made >> it into the Event Marker tab of the IADS Logs, did not disappear.
>> I hope that clarifies the problem we are seeing. However, we >> discovered another "feature" of this bug in yesterday's mission that >> explains why we did not see the problem until now. When the IADS Logs >> window is VISIBLE on the screen during the FES event, the Event Marker >> for the FES event is automatically dropped on the display AND the >> entry makes it into the Event Markers tab of the IADS Log. Because of >> real estate constraints, we usually run with the IADS Logs window >> minimized (not closed). When the IADS Logs window is minimized, the >> Event Marker for the FES event is automatically dropped on the display >> BUT the entry does not show up in the Event Markers tab of the IADS >> Logs. Late last year, after we had upgraded to IADS 7.2, the engineer >> who was the keeper of the Logs always had the IADS Logs window >> visible, so we did not think we had the issue with the FES events >> automatically making it into the Logs. We saw the issue this year >> when I became the "stuckee" who was responsible for keeping the Log >> and I had the IADS Logs window minimized.
>> However, in a post-test environment, the FES entries automatically >> make it into the Event Marker tab of the IADS Logs regardless of >> whether the IADS Logs window is visible or minimized. So, to >> replicate the problem, it appears you have to do it in a real time >> environment with the IADS Logs window minimized.
>> At least we have found a less distracting work-around for now.
>> -- >> You received this message because you are subscribed to the Google Groups >> "IADS" group. >> To post to this group, send email to iads@googlegroups.com. >> To unsubscribe from this group, send email to >> iads+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/iads?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "IADS" group. > To post to this group, send email to iads@googlegroups.com. > To unsubscribe from this group, send email to > iads+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/iads?hl=en.
> Thanx to your help, I think we cornered the problem. Apparently this bug > has been in Iads since the inception of "create EM at FES start" and > nobody has ever reported it (until now).
Correction. After further analysis, we've determined that this bug was introduced in release 7.0 (by me actually) while attempting to prevent an external configuration update from pausing the displays.
If anyone else is running into this problem please let us know. We've fixed the problem and are now in the processing of trying to get you a patch.
Sorry for the inconvenience, Jim
-------------------------------------------------- From: "James Bretz" <j...@iads-soft.com> Sent: Thursday, January 19, 2012 6:20 PM To: "IADS" <iads@googlegroups.com> Subject: Re: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
> Thanx to your help, I think we cornered the problem. Apparently this bug > has been in Iads since the inception of "create EM at FES start" and > nobody has ever reported it (until now).
> The problem occurs when the auto analysis creates an EventMarker without > the log being visible. If this occurs and an EventMarker is saved from > another user, the log entry gets erased (which of course shouldn't be > occurring).
> We'll fix this soon and follow up with a patch.
> The only workaround we can see right now is to leave the log visible (you > can position it almost completely off the screen).... You could also > manually create an Event Marker, but this would be more cumbersome.
> Sorry for the problems, > Jim
> -------------------------------------------------- > From: "James Bretz" <j...@iads-soft.com> > Sent: Thursday, January 19, 2012 10:35 AM > To: "IADS" <iads@googlegroups.com> > Subject: Re: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
>> David,
>> Actually, it was my wires that got crossed. TJ from the FQ group reported >> the other problem and I got it mixed up with Amy's post.
>> Thank you for the excellent description. I'll try to replicate this issue >> again. Sounds like you already cornered the problem (minimized log issue >> perhaps).
>> I'll get back to you ASAP, >> Jim
>> -------------------------------------------------- >> From: "David D" <david.k.d...@lmco.com> >> Sent: Thursday, January 19, 2012 9:54 AM >> To: "IADS" <iads@googlegroups.com> >> Subject: [IADS] Re: Adding Event Markers at FES Start with IADS 7.2
>>> Jim,
>>> It seems that wires got crossed somewhere. Refer to Amy's first post >>> where she says she DID have to move the event marker to get it to show >>> up in the log. We are using the exact same methods and having the >>> same issues. And for Michael Jones, I was using the exact same login >>> real time and post test.
>>> Let me try to describe the problem in excruciating detail so that it >>> is clear. When using FES to excite a mode in a flutter mission, we >>> want a marker to automatically be dropped at the FES start. To do so, >>> we turn on the Automated Analysis button on the dashboard so that it >>> reads "Automated Analysis Enabled". We also right-click above that >>> button and check "Add Event Marker at FES Start". There is no option >>> to automatically drop Test Point Markers at FES start and stop, so we >>> DO NOT use Test Point Markers.
>>> With the "Automated Analysis Enabled" and "Add Event Marker at FES >>> Start" checked, up until IADS 7.2 we would have both an event marker >>> dropped on the displays AND the event entry added to the Event Markers >>> tab in the IADS Logs at the start of the FES event. The Log entry >>> doesn't show up until the FES event is complete, but it is there. >>> Once we updated to version 7.2 of IADS, using the setup of "Automated >>> Analysis Enabled" and "Add Event Marker at FES Start" still drops the >>> Event Marker, but no entry is placed in the Event Marker tab of the >>> IADS Logs. To get the entry in the Event Marker tab of the IADS Logs, >>> you have to return to the displays and nudge the Event Marker (the >>> green line) slightly.
>>> If another discipline is using Test Point Markers or Event Markers >>> that get dropped at the same time, it is difficult to pick the FES >>> Event Marker from the 2+ overlaying markers. One time, I did not have >>> the Test Point Marker filters set up in the IADS Logs ahead of time to >>> filter out the Test Point Markers from other disciplines. When I >>> filtered the Test Point Markers after the FES event was complete so >>> that I could isolate the FES Test Point Marker to be able to nudge it, >>> the FES Test Point Marker disappeared completely. Those markers that >>> I had previously nudged (for earlier FES bursts) that had already made >>> it into the Event Marker tab of the IADS Logs, did not disappear.
>>> I hope that clarifies the problem we are seeing. However, we >>> discovered another "feature" of this bug in yesterday's mission that >>> explains why we did not see the problem until now. When the IADS Logs >>> window is VISIBLE on the screen during the FES event, the Event Marker >>> for the FES event is automatically dropped on the display AND the >>> entry makes it into the Event Markers tab of the IADS Log. Because of >>> real estate constraints, we usually run with the IADS Logs window >>> minimized (not closed). When the IADS Logs window is minimized, the >>> Event Marker for the FES event is automatically dropped on the display >>> BUT the entry does not show up in the Event Markers tab of the IADS >>> Logs. Late last year, after we had upgraded to IADS 7.2, the engineer >>> who was the keeper of the Logs always had the IADS Logs window >>> visible, so we did not think we had the issue with the FES events >>> automatically making it into the Logs. We saw the issue this year >>> when I became the "stuckee" who was responsible for keeping the Log >>> and I had the IADS Logs window minimized.
>>> However, in a post-test environment, the FES entries automatically >>> make it into the Event Marker tab of the IADS Logs regardless of >>> whether the IADS Logs window is visible or minimized. So, to >>> replicate the problem, it appears you have to do it in a real time >>> environment with the IADS Logs window minimized.
>>> At least we have found a less distracting work-around for now.
>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "IADS" group. >>> To post to this group, send email to iads@googlegroups.com. >>> To unsubscribe from this group, send email to >>> iads+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/iads?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "IADS" group. >> To post to this group, send email to iads@googlegroups.com. >> To unsubscribe from this group, send email to >> iads+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/iads?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "IADS" group. > To post to this group, send email to iads@googlegroups.com. > To unsubscribe from this group, send email to > iads+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/iads?hl=en.
