You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ability to exploit the high volumes of track data in these large datafiles
β° Business priority
Unclear for JW 21/2
We will typically require these items:
(Use convert to issue if it is to be delegated/assigned)
π Unique name for file format: Merlin ASAC
πΎ Obtain sample data (attach if allowable): Pending
π Exploitation plan for Merlin ASAC
π· Implementation
β Testing & Acceptance
Exploitation plan
We have a strange exploitation plan for this format. The analysts receive packages of 5 datafiles, each for a different type of data. The types include:
radar plot
IFF
AIS
EW Squarks
A N Other...
After a site visit to inspect the data, I believe the complexity of the formats, and the lack of a specification document for the data means I'm not confident of producing an unclass version of the data sufficient to give a reliable solution.
The plan for handling them is for clients to develop parser that converts files to Debrief format. The parser(s) will mature during JW 21/2. On completion we will take the parser and reverse-engineer datafiles to drive all paths through the parser.
The text was updated successfully, but these errors were encountered:
π Business value
β° Business priority
We will typically require these items:
(Use
convert to issue
if it is to be delegated/assigned)Exploitation plan
We have a strange exploitation plan for this format. The analysts receive packages of 5 datafiles, each for a different type of data. The types include:
After a site visit to inspect the data, I believe the complexity of the formats, and the lack of a specification document for the data means I'm not confident of producing an unclass version of the data sufficient to give a reliable solution.
The plan for handling them is for clients to develop parser that converts files to Debrief format. The parser(s) will mature during JW 21/2. On completion we will take the parser and reverse-engineer datafiles to drive all paths through the parser.
The text was updated successfully, but these errors were encountered: