LuciadFusion Samples

This sample generates a list of data models trees. The data models contain all declared properties of all declared types inside the data model. The sample can generate strings for any given property, which can then be used in conjunction with a TLcdDataObjectExpressionLanguage to generate a value for a data object of the selected data type.

Instructions

Click on any of the data types on the left. This will generate a tree in the center of the frame. Each tree contains a list of properties. By clicking on a property, you generate a string that is visible in the textarea on the bottom of the frame.

A property itself also has a data type that in turn can have its own list of properties.

This sample decodes an ASDI file, which contains information in the form of trajectories and flight plan history objects. For each trajectory, a track is created that represents that trajectory at a certain point in time. This time can be controlled by the Simulator control panel at the bottom of the window. When selecting a track, the trajectory corresponding with the track is also selected and the flight plan associated with the track at the current time is added to the map.

You can view the detailed properties of a track or associated flight plan by selecting a track.

Instructions

You can open an ASDI file using the "Open" button on the toolbar. Some sample data is available in the LuciadLightspeed distribution.

To view the details of an ASDI track and associated flight plan, click on it and a popup will appear with the details.

You can use the controls at the bottom of the page to control the simulation:

• Press the Run button to start the simulation. The tracks will start moving.
• Press the Pause button to pause the simulation when it is running. The tracks will stop moving.
• Press the Stop button to stop the simulation. All tracks will be reset to their initial position.
• When the simulation is not running, drag the time slider to change the simulation time. The position of the tracks will be updated according to this simulation time.
• Change the "% CPU" slider the maximum percentage of CPU used for the simulation application Setting this to a lower value will result in a less smooth simulation.
• Change the "Speed-up" slider to change how much faster "simulation time" flows with respect to "real time". For instance, when set to 60, one minute of "simulation time" will tick by every second. Setting this value higher will make the tracks move faster.

Zoom in to see the labels of the tracks. After that you can move the text-labels by

• enabling the select controller in the toolbar
• moving your mouse cursor over one of the text-labels
• clicking and dragging the text-label

This sample will process the ASDI file so that the ASDI live decoder can replay the data as if it were live data. The decoder will maintain a list of tracks and update them according to the information it receives from the live InputStream. As stated above, in this sample this live InputStream will be derived from an ASDI file.

When you select a track that has flight plan information associated with it, the associated flight plan is added to the map.

When you select a track, more information about the track and associated flight plan will be shown in a popup.

Instructions

The sample will open a predefined ASDI file and start replaying that.

To view the details of an ASDI track and associated flight plan, click on the track and a popup will appear with the details.

Zoom in to see the labels of the tracks. After that you can move the text-labels by

• enabling the select controller in the toolbar
• moving your mouse cursor over one of the text-labels
• clicking and dragging the text-label

This sample generates a list of data models trees. The data models contain all declared properties of all declared types inside the data model. The sample can generate strings for any given property, which can then be used in conjunction with a TLcdDataObjectExpressionLanguage to generate a value for a data object of the selected data type.

Instructions

Select data types on the top. This will generate a tree in the center of the frame. Each tree contains a list of properties. By clicking on a property, you generate a string that is visible in the textarea on the bottom of the frame.

A property itself also has a data type that in turn can have its own list of properties.

This sample decodes an asterix file, which contains information in the form of trajectories. For each of these trajectories, a track is created that represents that trajectory at a certain point in time. This time can be controlled by the Simulator control panel at the bottom of the window.

Since ASTERIX data usually is relative with respect to a radar, the positions of the radars must be specified. These positions can be entered in the locations.cfg file. If you have your own ASTERIX data you wish to load, you will need to add the locations of your radars to this file.

Furthermore you can view the detailed properties of a track by double-clicking on it.

Each track is labeled with its track number when zoomed in. The labels avoid overlap in a continuous fashion by moving the labels around gently. In the event labels get mixed up, they can be dragged to a new location, after which they move back automatically.

Instructions

Press the "Open" button on the toolbar to open an ASTERIX file. Some sample data is available in the LuciadLightspeed distribution. If you have your own ASTERIX data you wish to load, you will need to add the locations of the radars to the locations.cfg file.

Click on an ASTERIX track to view the details on it in a popup.

You can use the controls at the bottom of the page to control the simulation:

• Press the Run button to start the simulation. The tracks will start moving.
• Press the Pause button to pause the simulation when it is running. The tracks will stop moving.
• Press the Stop button to stop the simulation. All tracks will be reset to their initial position.
• When the simulation is not running, drag the time slider to change the simulation time. The position of the tracks will be updated according to this simulation time.
• Change the "Speed-up" slider to change how much faster "simulation time" flows with respect to "real time". For instance, when set to 60, one minute of "simulation time" will tick by every second. Setting this value higher will make the tracks move faster.

Zoom in to see the labels of the tracks. After that you can move the text-labels by

• enabling the select controller in the toolbar
• moving your mouse cursor over one of the text-labels
• clicking and dragging the text-label

Furthermore, the sample demonstrates the use of ALcdASTERIXReferenceProvider to supply the position of the radar platform, which is not included in ASTERIX category 240 data. Finally, it also illustrates the various styling options that are available for radar video layers.

Instructions

The styling of the radar layers can be configured using the controls in the bottom right panel. You can change the following properties of the styling:

• Colors: change the color of the background, sweep and blips.
• Afterglow duration in seconds: increasing this creates a "history trail" effect on the blips.
• Intensity: increasing this makes blips with a low amplitude stand out more.
• Threshold: the minimum amplitude required for a blip to be displayed. Increase this to filter out unwanted noise.
• Enable or disable the sweep and grid lines.

Instructions

The sample shows a track display view, populated with tracks. Each track has a history trail and a label with some information in it. It is possible to hover over or highlight certain tracks by clicking on their icon. Once a track is highlighted, it is displayed using a different icon and it has more content in its label. Among this new content is a comments field which can be modified by clicking on it. Track labels can be moved by dragging them with the middle mouse button.

Track labels have the following content:

• Target address (Cat 21) or Track Number (Cat 62)
• Flight level
• Ground speed, in kilometers per hour
• Mode 3/A code (on hover or when highlighted)
• Custom text (on hover or when highlighted), can be modified when highlighted

In general, the implementation for the labels of this track display aims to keep labels as stable as possible. Zooming and panning should not affect the label locations, pin lines should not move when a track is highlighted, etc... This way, the sample tries to reduce noise as much as possible. This for example explains why labels can be only partially visible at the edge of the map.

This sample will process the ASTERIX final file so that the ASTERIX live decoder can replay the data as if it were live data. The decoder will maintain a list of tracks and update them according to the information it receives from the live InputStream. As stated above, in this sample this live InputStream will be derived from a final ASTERIX file.

Since ASTERIX data usually is relative with respect to a radar, the positions of the radars must be specified. These positions can be entered in the locations.cfg file. If you have your own ASTERIX data you wish to load, you will need to add the locations of your radars to this file.

Each track is labeled with its track number when zoomed in. The labels avoid overlap in a continuous fashion by moving the labels around gently. In the event labels get mixed up, they can be dragged to a new location, after which they move back automatically.

When you double-click on a track, detailed properties will be shown in a popup.

Instructions

The sample opens a predefined ASTERIX file and starts replaying it.

Double-click on an ASTERIX track to view the details on it in a popup.

Zoom in to see the labels of the tracks. After that you can move the text-labels by

• enabling the select controller in the toolbar
• moving your mouse cursor over one of the text-labels
• clicking and dragging the text-label