# GeoSlicer on HPC

**URL:** <https://discourse.slicer.org/t/geoslicer-on-hpc/43316>\
**Category:** Support\
**Created:** [June 11, 2025, 3:59pm UTC](https://discourse.slicer.org/t/geoslicer-on-hpc/43316 "2025-06-11T15:59:03Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![fbordignon](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fbordignon/32/5269_2.png) [@fbordignon](https://discourse.slicer.org/u/fbordignon)\
**Post date:** [June 26, 2025, 2:13pm UTC](https://discourse.slicer.org/t/geoslicer-on-hpc/43316/4 "2025-06-26T14:13:35Z")

</div>

Alright, for future reference our slurm job monitor is implemented using a view:

> <https://github.com/petrobras/GeoSlicer/blob/main/src/modules/JobMonitor/JobMonitor.py>

and a model with the logic:

> <https://github.com/petrobras/GeoSlicer/blob/main/src/ltrace/ltrace/remote/jobs.py>

There is the need to implement a specific handler for each use case different than ours.

---

_[View the full topic](https://discourse.slicer.org/t/geoslicer-on-hpc/43316)._