[EISA] OMEA Test 7, 9, and 11 -ok

[John M Slaby]

Gents,
I need a modification to the database schema for the primary table - could
you change the microsecond field from a date to an integer. The seconds
field is fine as a date now, but the microsecond field is still an
integer.
Thanks,
John 


John M. Slaby

Chief Engineer, ASPEN
978.440.1216 (W)
508.954.6461 (C)

-----Original Message-----
From: Sutherland, Hunt A (GE, Research) [mailto:sutherland at crd.ge.com] 
Sent: Friday, January 16, 2009 9:01 AM
To: John M Slaby; James Hill; Thomas Silveria
Cc: eisa at list.isis.vanderbilt.edu
Subject: RE: OMEA Test 7, 9, and 11 -ok


Tom did a nice job with setup and run of scenarios. For John's purpose I
will rerun the EISA framework to produce a replacement UserAppDAA.db_ with
the Windows build of EISA.

The log file looks good other than it looks like the UserAppDAA goes away
when running with the CUTS.  Nor do I see any CORBA exceptions.  A problem
I have not seen with the Windows build.

Hunt

-----Original Message-----
From: Thomas Silveria [mailto:Thomas_Silveria at raytheon.com]
Sent: Thursday, January 15, 2009 6:42 PM
To: Thomas Silveria
Cc: eisa at list.isis.vanderbilt.edu; James Hill; John M Slaby; Sutherland,
Hunt A (GE, Research)
Subject: OMEA Test 7, 9, and 11

Hi Gentlemen;
It seems that we have data.



The attached db11.3.xxx file was created as a winzip file and contains the
following:
  - DAC1.db_, DAC2.db_, DAC3.db_, DAC4.db_, UserAppDAA.db_, and
userApp_client1_foil.log

I ran the following tests:
  - First I ran Test 7 for 2 minutes it shows up in the DACX.db_ files as
test 5,
  - Then I ran Test 9 for 2 minutes it shows up in the DACX.db_ files as
test 9,
  - I then killed everything and did not delete the .db_ files,
  - I started the cuts_node.pl tee'ed to userApp_client1_foil.log,
  - Finally I ran Test 11 for 15 seconds it shows up in the DACX.db_ files
as test 5 again.


If you look at DAC3.db_ you can see the following similar patterns in
Datadesc:
  - The wrong testid.
  - The time_s when changing from test 5 to test 9 seems to be skewed by
one row.

Moving to DAC1.db_ you can see the following in DataDesc:
  - time_s is skewed by 29 rows when changing from test 5 to test 9.

DAC1.db_ Metadata is correctly showing me that the tg_E got it's
Component_State_Probe in the database DAC2.db_, DAC3.db_, and DAC4.db_
Metadata is correctly not showing a Component_State_Probe in the database

Registration has the correct uuid and name as far as I've checked.

Please contact me via cell phone until Monday morning:  1-401-243-7726

Thanks:
Tom


Thomas Silveria
Senior Software Engineer, Athena MDA
Raytheon Integrated Defense Systems

401.842.5191 office
444.5191 tie line
401.842.5265 fax
Thomas_Silveria at Raytheon.com

1847 West Main Road
Constitution, C11, 3-1-C031
Portsmouth, RI   02871-1087, USA