173 posts tagged with "Foxglove"

🛎️ List available services from ROS and custom Foxglove websocket connections​

When streaming live data for visualization over the Foxglove bridge, the available services are now listed in the Service Call panel.

☁️ Quickly access recent cloud data sources​

Recently accessed cloud data sources will now show in the "recent sources" list on both the dashboard and the left-hand menu. These sources will be marked with a ☁️ icon.

🔗 Construct shareable links using your device name​

You can now create shareable links using ds.deviceName to refer to data associated with one of your devices using the name you gave it in Foxglove. For example, to create a shareable link that visualizes data from my-device between specified start and end times with the layout ID abc123, use the following parameters:

ds.deviceName=my-device
ds.start=2024-04-18T16:26:41.371Z
ds.end=2024-04-18T16:30:51.055Z
ds.layoutId=abc123

The URL will look like this and can be shared with anyone in the my-org organization:

https://app.foxglove.dev/my-org/view?ds=foxglove-stream&ds.deviceName=my-device&ds.start=2024-04-18T16%3A26%3A41.371Z&ds.end=2024-04-18T16%3A30%3A51.055Z&layoutId=abc123

Note that parameters must be URL encoded, so for example 2024-04-18T16:26:41.371Z becomes 2024-04-18T16%3A26%3A41.371Z.

🍎 Performance gains on macOS​

The Foxglove desktop app on Mac now uses Metal, a high-performance graphics API developed by Apple. By using Metal, we're now able to reduce CPU overhead and get nearly direct access to GPU resources for significant performance gains.

Downloads: Linux: deb amd64 arm64, snap amd64 | Windows: Universal | Mac: Universal

This release contains some minor bug fixes.

Downloads: Linux: deb amd64 arm64, snap amd64 | Windows: Universal | Mac: Universal

✏️ Renaming Tab panels​

We’ve made it easier to rename Tab panels. The Tab panel can be helpful for organizing complex layouts where you need lots of information at hand without switching layouts.

🚨 Better handling of conflicting message schemas​

Robotic systems are complex and multi-faceted. It’s occasionally possible to accidentally introduce two different versions of the same schema on the same robot system. To help with this, we added friendly error messages that surface in the Problems sidebar when conflicting duplicate schema names are found in an MCAP file and cause replay issues.

Downloads: Linux: deb amd64 arm64, snap amd64 | Windows: Universal | Mac: Universal

This release contains some minor bug fixes.

🤏 Customize table views​

You can now manage and resize table columns on the Device and Event tables to customize how you view your data.

⏱️ RFC 3339 and 24-hour time formats​

Visualization playback now supports displaying timestamps in RFC 3339 (ISO 8601) and 24-hour formats in addition to 12-hour and epoch.

✍️ Renamed NPM package​

When we launched Foxglove 2.0, we dropped the "Studio" name. In keeping with that, we renamed the @foxglove/studio NPM package to @foxglove/extension. Please update your custom extensions to depend on @foxglove/extension to receive future SDK updates.

📞 Better ROS Service call integration​

We’ve improved the Foxglove client integration with ROS Services to allow Foxglove to be aware if a service is unavailable and the service has failed. The Foxglove websocket protocol now has a serviceCallFailure operation that can communicate to custom panels or the Foxglove Service Call panel when a call fails.

📈 Resizable reference lines in the Plot panel​

Did you know you can create reference lines in the Plot panel? Now you can adjust the size of reference lines to improve their visibility.

📹 Low-latency multi-video playback​

Buckle up for smoother video loading: We've made performance improvements to video playback so you get a low latency experience when visualizing multiple CompressedVideo topics at once.

3D​

Have you ever wanted to get a 3D view of the entire world? One of our users did, but had some issues with z-fighting that kept the visualization within Foxglove from looking as sharp as it should. We think that outer-space fighting should be limited to intergalactic battles, so we added a new setting to enable a logarithmic depth buffer, which can improve rendering precision for large distance scales.

Using this feature may lead to a loss in rendering performance, but may be worth the price for users looking to visualize Earth-scale data, large maps, or just wanting to zoom in/out really, really far.

In this example below:

• The left pane does not use logarithmic depth, and it has a near clipping plane of 1.0. The grids render smoothly, but objects close to the viewer are clipped.
• The middle pane does not use logarithmic depth, and has a near plane of 0.01. The viewer can get closer to objects without clipping, but rendering artifacts (z-fighting) appear between multiple grids.
• The right pane enables the new logarithmic depth setting. This avoids z-fighting by providing more depth precision for the grids, while still allowing a near plane value of 0.01 for reduced clipping.

Services​

The Service Call panel now has an option to hide the request and response text fields. This allows you to configure a request once up front, then invoke the service call without any distractions. We love distractions, but only the kinds that have wet noses and wagging tails.

JSON data sources​

• When using a WebSocket connection, JSON channels and services with no schema are now supported (using an empty string for the schema name and data).
• Added support for fixed-length arrays (specified with prefixItems).

Stability and usability​

• The web application no longer encounters errors when a new version is released while the app is already open.
• Various usability enhancements to Recordings, General and Team settings, Webhooks, data playback while buffering, and deep linking.
• Improvements to error messages for opening incompatible files and layouts, and for WebSocket connections that encounter unexpected server behavior.

User scripts​

• Improvements to user scripts to allow returning types that consist of  fields or fields with types:

type Output = {
  field1: Message<"std_msgs/String">;
  field2: Array<number>;
};

It is now possible to create elaborate return types, for example:

import { Input, Message, Time } from "./types";
import { subtractTimes } from "./time";

type InputType = Message<"geometry_msgs/PoseStamped">;
type Output = {
  header: InputType["header"];
  time_diff: Time;
  translation: Message<"geometry_msgs/Vector3">;
  random_array: Array<number>;
};

export const inputs = ["/pose_stamped"];
export const output = "/pose_difference";

let lastMessage: InputType | undefined;

// Calculates translation & time difference between two subsequent poses.
export default function script(event: Input<"/pose_stamped">): Output | undefined {
  const message = event.message;

  if (!lastMessage) {
    lastMessage = message;
    return undefined;
  }

  const output: Output = {
    header: message.header,
    time_diff: subtractTimes(message.header.stamp, lastMessage.header.stamp),
    translation: {
      x: message.pose.position.x - lastMessage.pose.position.x,
      y: message.pose.position.y - lastMessage.pose.position.y,
      z: message.pose.position.z - lastMessage.pose.position.z,
    },
    random_array: [Math.random(), Math.random()],
  };

  lastMessage = message;
  return output;
}

Snap package​

• Added interface to support using Foxglove with gamepads via the Snap Store.

Performance​

• Playback performance improvements when buffering data.

Plan management​

• Fixed some minor issues with plan management and limits.