# 2024.08.20 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2024-08-20-weekly-meeting/37956>\
**Category:** Weekly meetings\
**Created:** [August 20, 2024, 1:10pm UTC](https://discourse.slicer.org/t/2024-08-20-weekly-meeting/37956 "2024-08-20T13:10:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [August 20, 2024, 1:10pm UTC](https://discourse.slicer.org/t/2024-08-20-weekly-meeting/37956/1 "2024-08-20T13:10:01Z")

</div>

Today, we will be having our next weekly hangout at **10:00 AM ET until 11:00 AM ET**

Anyone is welcome to join at this link: [https://bit.ly/slicer-googlemeet-hosted-by-kitware](https://bit.ly/slicer-googlemeet-hosted-by-kitware)

* * *

> **Weekly Meeting**
>
> **Starts:** August 20, 2024, 10:00am (America/New\_York)\
> **Link:** <https://bit.ly/slicer-googlemeet-hosted-by-kitware>

**Agenda:**

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

* * *

Thanks  
Sam and J-Christophe

---

<div class="post-metadata">

**Author:** ![BerDom.Ing](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/berdom.ing/32/69496_2.png) [@BerDom.Ing](https://discourse.slicer.org/u/BerDom.Ing)\
**Post date:** [August 20, 2024, 1:25pm UTC](https://discourse.slicer.org/t/2024-08-20-weekly-meeting/37956/2 "2024-08-20T13:25:47Z")

</div>

I would like to show the advancements of the telemetry front end

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 20, 2024, 10:32pm UTC](https://discourse.slicer.org/t/2024-08-20-weekly-meeting/37956/3 "2024-08-20T22:32:04Z")

</div>

### Meeting Notes

#### Reusable GitHub Workflow

The `commit-message.yml` workflow has been updated to support reuse across other workflows. For details, see the pull request: [Slicer PR #7898](https://github.com/Slicer/Slicer/pull/7898).

#### Displaying Popups from Regular Python Scripts

During the review of [SlicerIDCBrowser PR #43](https://github.com/ImagingDataCommons/SlicerIDCBrowser/pull/43), we explored methods to enable the use of Qt APIs, such as message boxes, within standard Python scripts. The following approaches were discussed:

- Launching Slicer with `--python-code`, `--no-main-window`, `--disable-modules`, and `--exit-after-startup` command line options.
- Installing _Qt for Python_.
- Enhancing the CTK application launcher by adding a command line option like `--display-message`.
- Creating a lightweight Slicer Qt application named “PythonQt” to execute scripts and allow importing `qt` and `ctk` Python wrappers, similar to the GUI Console.

#### Telemetry

Enhancing Event Data Transmission:

- Optimize the event data sent to the server by aggregating events on a daily basis.

Adjusting Map Granularity:

- Refine the map’s granularity to display data at the city level.

Simulating Data Upload:

- Simulate data uploads from various Slicer applications for testing and analysis.

#### SlicerSOFA Extension

- The SlicerSOFA extension enables the translation of transformations occurring in the simulation space (typically involving 3D models) into medical images and segmentations. An example demonstrating this capability will be included in an upcoming update to the extension.