Aspam display issue

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Aspam display issue

Morrin, Damon

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real “name” because the extension is following the 2nd period.

 

Damon C Morrin

Senior Software Engineer

Ball Aerospace & Technologies Corp.

2875 Presidential Drive, Suite 180

Fairborn, OH 45324

937-320-6019 

[hidden email]   

 


This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.
Reply | Threaded
Open this post in threaded view
|

RE: Aspam display issue

Kip Streithorst
Administrator
In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: Aspam display issue

Jonathan Overholser
Since we don't have control over the initial creator I'm suggesting we implement option 1 or 2.

Jon

-----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: Aspam display issue

Johnson, Todd
In reply to this post by Kip Streithorst
For what it's worth, Windows Explorer only considers characters after the last period to be part of the extension. For example, if you create a file called foo.bar.baz, Windows Explorer will show the file type as "BAZ File."

Todd Johnson

-----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: Aspam display issue

tclarke
Administrator
In reply to this post by Kip Streithorst
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm generally in favor of 2 but I'm never been fond of using the full path as the name...the full path is more consistent with some of the other importers. There isn't really a way to get a dataset name from the ASPAM file itself...we could perhaps generate something from paragraphs A and B (the site location and collect time) but it might be difficult for an analyst to tie the filename to the site/time information.

- -----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

- ---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFH+l3j+xUTKUxH/LkRAjGUAJ9aXdqCVn5uJcnkWno2D4F/IV0HjACgqFeG
5ThqtsQ9LfS9qiCTclqHWpM=
=B1Yb
-----END PGP SIGNATURE-----



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: RE: Aspam display issue

Kip Streithorst
Administrator
In reply to this post by Johnson, Todd
The problem is kind of a quagmire as noticed by the fact that Qt has two functions on QFileInfo, baseName() and completeBase() to return "foo" and "foo.bar" respectively for your example.

Thanks,
Kip

-----Original Message-----
From: Johnson, Todd [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:34 PM
To: [hidden email]
Subject: RE: RE: Aspam display issue

For what it's worth, Windows Explorer only considers characters after the last period to be part of the extension. For example, if you create a file called foo.bar.baz, Windows Explorer will show the file type as "BAZ File."

Todd Johnson

-----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: RE: Aspam display issue

Kip Streithorst
Administrator
In reply to this post by tclarke
I would prefer option 1 because it's more consistent with other importers, but I could live with option 4 and then option 2 in that order.

Thanks,
Kip

-----Original Message-----
From: Clarke, Trevor [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:46 PM
To: [hidden email]
Subject: RE: RE: Aspam display issue

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm generally in favor of 2 but I'm never been fond of using the full path as the name...the full path is more consistent with some of the other importers. There isn't really a way to get a dataset name from the ASPAM file itself...we could perhaps generate something from paragraphs A and B (the site location and collect time) but it might be difficult for an analyst to tie the filename to the site/time information.

- -----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

- ---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFH+l3j+xUTKUxH/LkRAjGUAJ9aXdqCVn5uJcnkWno2D4F/IV0HjACgqFeG
5ThqtsQ9LfS9qiCTclqHWpM=
=B1Yb
-----END PGP SIGNATURE-----



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: RE: Aspam display issue

Sulgrove, David
A benefit of using Option 1, where the data element name is set as the full path and name, is that Opticks automatically sets the element's display name as the filename in the format of Option 2.

David Sulgrove
Ball Aerospace & Technologies Corp.


-----Original Message-----
From: Streithorst, Kip
Sent: Monday, April 07, 2008 1:49 PM
To: [hidden email]
Subject: RE: RE: RE: Aspam display issue

I would prefer option 1 because it's more consistent with other importers, but I could live with option 4 and then option 2 in that order.

Thanks,
Kip

-----Original Message-----
From: Clarke, Trevor [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:46 PM
To: [hidden email]
Subject: RE: RE: Aspam display issue

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm generally in favor of 2 but I'm never been fond of using the full path as the name...the full path is more consistent with some of the other importers. There isn't really a way to get a dataset name from the ASPAM file itself...we could perhaps generate something from paragraphs A and B (the site location and collect time) but it might be difficult for an analyst to tie the filename to the site/time information.

- -----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

- ---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFH+l3j+xUTKUxH/LkRAjGUAJ9aXdqCVn5uJcnkWno2D4F/IV0HjACgqFeG
5ThqtsQ9LfS9qiCTclqHWpM=
=B1Yb
-----END PGP SIGNATURE-----



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: RE: RE: Aspam display issue

Kip Streithorst
Administrator
I think this option because it will forbid the import of the same ASPAM twice.  But this has the added bonus of showing a filename like option 2 in the session explorer and if we change the AspamViewer to use SessionItem::getDisplayName() instead of SessionItem::getName(), we'll also see the shortened option 2 name in the AspamViewer.  What does everyone else think?

Thanks,
Kip

-----Original Message-----
From: Sulgrove, David [mailto:[hidden email]]
Sent: Thursday, April 10, 2008 1:25 PM
To: [hidden email]
Subject: RE: RE: RE: Aspam display issue

A benefit of using Option 1, where the data element name is set as the full path and name, is that Opticks automatically sets the element's display name as the filename in the format of Option 2.

David Sulgrove
Ball Aerospace & Technologies Corp.


-----Original Message-----
From: Streithorst, Kip
Sent: Monday, April 07, 2008 1:49 PM
To: [hidden email]
Subject: RE: RE: RE: Aspam display issue

I would prefer option 1 because it's more consistent with other importers, but I could live with option 4 and then option 2 in that order.

Thanks,
Kip

-----Original Message-----
From: Clarke, Trevor [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:46 PM
To: [hidden email]
Subject: RE: RE: Aspam display issue

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm generally in favor of 2 but I'm never been fond of using the full path as the name...the full path is more consistent with some of the other importers. There isn't really a way to get a dataset name from the ASPAM file itself...we could perhaps generate something from paragraphs A and B (the site location and collect time) but it might be difficult for an analyst to tie the filename to the site/time information.

- -----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

- ---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFH+l3j+xUTKUxH/LkRAjGUAJ9aXdqCVn5uJcnkWno2D4F/IV0HjACgqFeG
5ThqtsQ9LfS9qiCTclqHWpM=
=B1Yb
-----END PGP SIGNATURE-----



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: RE: RE: RE: Aspam display issue

Morrin, Damon
Seems like the best option

-----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Thursday, April 10, 2008 2:01 PM
To: [hidden email]
Subject: RE: RE: RE: RE: Aspam display issue

I think this option because it will forbid the import of the same ASPAM twice.  But this has the added bonus of showing a filename like option 2 in the session explorer and if we change the AspamViewer to use SessionItem::getDisplayName() instead of SessionItem::getName(), we'll also see the shortened option 2 name in the AspamViewer.  What does everyone else think?

Thanks,
Kip

-----Original Message-----
From: Sulgrove, David [mailto:[hidden email]]
Sent: Thursday, April 10, 2008 1:25 PM
To: [hidden email]
Subject: RE: RE: RE: Aspam display issue

A benefit of using Option 1, where the data element name is set as the full path and name, is that Opticks automatically sets the element's display name as the filename in the format of Option 2.

David Sulgrove
Ball Aerospace & Technologies Corp.


-----Original Message-----
From: Streithorst, Kip
Sent: Monday, April 07, 2008 1:49 PM
To: [hidden email]
Subject: RE: RE: RE: Aspam display issue

I would prefer option 1 because it's more consistent with other importers, but I could live with option 4 and then option 2 in that order.

Thanks,
Kip

-----Original Message-----
From: Clarke, Trevor [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:46 PM
To: [hidden email]
Subject: RE: RE: Aspam display issue

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm generally in favor of 2 but I'm never been fond of using the full path as the name...the full path is more consistent with some of the other importers. There isn't really a way to get a dataset name from the ASPAM file itself...we could perhaps generate something from paragraphs A and B (the site location and collect time) but it might be difficult for an analyst to tie the filename to the site/time information.

- -----Original Message-----
From: Streithorst, Kip [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:21 PM
To: [hidden email]
Subject: RE: Aspam display issue

In general, Opticks and Qt consider filenames to broken up as follows.  If a file was named C:\Foo\Bar\AAA.BBB.CCC.DDD, then Opticks and Qt would consider C:\Foo\Bar to be the file path, AAA to be name of the file and BBB.CCC.DDD to be the file extension.  What you are seeing is that the Aspam Viewer decides to name the Aspam Element in Model Services using the file name or AAA.  My initial inclination would be to leave this behavior alone and suggest that the creator of your Aspam's not use a spurious period.  If that is not suitable I provide the following options for naming the Aspam element in ModelServices:

1) Use the full path and name (i.e. C:\Foo\Bar\AAA.BBB.CCC.DDD) - this is most consistent with our other importers
2) Use the full name (ie. AAA.BBB.CCC.DDD)
3) Leave the current behavior (ie. AAA )
4) Do something smarter, like only remove known ASPAM extensions (ie. only remove PAR and WXDATA if present)
5) If don't know if this is possible, but look inside the ASPAM to determine it's name.

Keep in mind that whatever solution is picked affects the ability to load other ASPAMs.  For example if option 3 is chosen, then 13Nov2008.WXDATA and 13Nov2008.PAR could not be loaded at the same time, because both would attempt to create an element in ModelServices called 13Nov2008.

What does everyone else think?

Thanks,
Kip

________________________________________
From: Morrin, Damon [mailto:[hidden email]]
Sent: Monday, April 07, 2008 1:13 PM
To: [hidden email]
Subject: Aspam display issue

When an Aspam is displayed with the Aspam Viewer the name is truncated after the first period that is found.  In the case of ingested weather files they have 2 periods in the name and this is truncating part of the real "name" because the extension is following the 2nd period.

Damon C Morrin
Senior Software Engineer
Ball Aerospace & Technologies Corp.
2875 Presidential Drive, Suite 180
Fairborn, OH 45324
937-320-6019 
[hidden email]   




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

- ---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFH+l3j+xUTKUxH/LkRAjGUAJ9aXdqCVn5uJcnkWno2D4F/IV0HjACgqFeG
5ThqtsQ9LfS9qiCTclqHWpM=
=B1Yb
-----END PGP SIGNATURE-----



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]