Continuing from the previous article regarding support for non-time datasets, we’re now going to consider how to collate two non-time indexed dataset to produce a 2D dataset that can be displayed as a heat map. Background The big picture objective is to view a two-dimensional plot containing the signal strength from a transmitter (tx) mapped
A shortcoming of the initial backend datastore for Limpet (learn more here: http://limpet.info) was that it could only store datasets that were indexed by time. This had little impact, since Limpet was only being used for analysis of time-stamped data. But, for the second phase of support for multi-static analysis, Limpet must store data indexed
Last year’s addition of Stacked Charts in Debrief started the movement towards more free-flowing analysis using Debrief. Stacked Charts allowed the analyst to consider the relationships between any kind of data in Debrief. Traditionally Debrief had a tightly focused data model: platform tracks plus some sensor data. While new graphical annotations and cosmetic styling of
For the last year we’ve been steadily progressing Debrief’s data analysis capabilities (read last year’s introduction here), adding features in packages focussed on analysts’ requirements. The first major realisation of this is in Debrief’s new Tactical Overview display, which will be released later on today. This posting will give you an overview of the capability.
Commenting on a Debrief Issue Commenting on any open or closed Debrief issue, whether your own or anyone else’s, is easy to do: Click on the Subject line of the issue you wish to comment on to view the issue: The issue will then display: As the above image shows, there is a comment box
Editing or Deleting Debrief Issues and Comments in GitHub In this post, we’re going to cover editing and deleting issues and comments on issues in GitHub. Considering what we’ve already covered, you should hopefully be quite familiar with where everything is in GitHub now, and this should be a breeze. Editing an Issue or Comment
Viewing Debrief Issues in GitHub Viewing an Issue in Debrief/GitHub is very easy to do and though it’s not necessary to log into GitHub to view issues it is required if you wish to raise an issue. Navigate to the Debrief repository: Click on the Issues tab to view the list of all current issues.
Notifying Changes to Debrief Now we will look at notifying changes to Debrief. As we’ve mentioned already, Debrief has been under continuous maintenance for 20-years now and, as you can imagine, has evolved considerably over that time. As it is open source and hosted on GitHub, anyone can take a copy of the main repository
Creating a Debrief Issue If you find that Debrief isn’t behaving as it should then it’s possible that you’ve encountered a bug in the software. If you do, then you’ll need to let the Debrief team know about it so they can fix it. We report bugs in the software by raising what is called
Obtaining Debrief Support Debrief is a capable, fast, intuitive and immensely powerful tool for maritime analysis. Indeed, as well as being used by many navies around the world, it’s also used by governmental and non-governmental agencies in many countries. Being open-source software, it is free to use; it works on multiple platforms; is well-documented with