# 2019.08.06 Hangout

**URL:** <https://discourse.slicer.org/t/2019-08-06-hangout/7893>\
**Category:** Weekly meetings\
**Created:** [August 6, 2019, 12:10pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893 "2019-08-06T12:10:58Z")\
**Posts on this page:** 5\
**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 6, 2019, 12:10pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893/1 "2019-08-06T12:10:58Z")

</div>

Hi,

Today, we will be having our weekly hangout at 10:00 AM EST until 11 AM.

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

Thanks  
Sam

---

<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 6, 2019, 2:29pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893/2 "2019-08-06T14:29:27Z")

</div>

## Minutes

### Recapping events from last week

- Steve Pieper went to SIGGRAPH  
-Lots of open source stuff
- Sam Horvath and JC taught the advanced slicer training course at Kitware

### Slicer Updates

- Steve has been investigating ITK update effects on the extensions
- We are going to look at grabbing the cdash results for the extensions through REST for additional processing to help with tracking extension build issues

---

<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 6, 2019, 4:02pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893/3 "2019-08-06T16:02:36Z")

</div>

> [@Sam\_Horvath](#):
>
> through REST for additional processing to help with tracking extension build issues

Here is a notebook I created a while back that is using REST API to collect data from CDash. See [https://nbviewer.jupyter.org/github/jcfr/jupyter-notebooks/blob/master/01\_Collect\_Slicer\_Dashboard\_Stats.ipynb](https://nbviewer.jupyter.org/github/jcfr/jupyter-notebooks/blob/master/01_Collect_Slicer_Dashboard_Stats.ipynb)

---

<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 6, 2019, 5:00pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893/4 "2019-08-06T17:00:47Z")

</div>

This is great, thanks!

I am thinking about creating a page that displays something similar to the table in the notebook, auto-generated each day after the builds are (hopefully) finished. I will probably do something quick/lazy with github pages to get it up and running.

---

<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 6, 2019, 6:48pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893/5 "2019-08-06T18:48:53Z")

</div>

> displays something similar to the table in the notebook, auto-generated each day after the builds are (hopefully) finished  
> I will probably do something quick/lazy with github pages to get it up and running.

Makes sense.

Some history: When we used to automatically update the wiki after the build are completed, we were running [this script](https://github.com/Slicer/slicer-wiki-scripts#slicer_wiki_extension_module_listingpy) on each factory, and then we were consolidating all gathered information later that day. This was not very robust.

A simple approach could be to setup a recurrent travis cronjob, that would generate the tables for the current day and previous day every hours. I can point you to an example of such job that is already publishing github pages (this is what we do for the apidocs)

> re: CDash API

Here is some other relevant discussion: [How can I subscribe to monitor individual extensions on Slicer dashboard? - #5 by fedorov](https://discourse.slicer.org/t/how-can-i-subscribe-to-monitor-individual-extensions-on-slicer-dashboard/2261/5)