Verified Commit ee34748a authored by Dworatzyk, Katharina's avatar Dworatzyk, Katharina Committed by Huste, Tobias (FWCC) - 111645
Browse files

Replace individual plots with subplot figures

parent e35b5160
......@@ -20,26 +20,26 @@ excerpt:
"
---
### Survey outreach
In the beginning of 2020, the HIFIS Software Survey was conducted to learn about current software development practices
within Helmholtz and to assess the demand for specific services to support researchers in their day-to-day work.
For the community team, it was particularly important to get a better grasp of who and to better understand their needs of
One approach to the data was to draw a picture of the "typical" research software developer, to evaluate support currently provided
and to identify more specific challenges that should be addressed in our future work.
### Software made by Helmholtz
Seventeen of the 19 Helmholtz centers and 3 external researchers participated in this survey, providing 467 individual responses.
With about 42.000 employees within Helmholtz we can say that at least 1% are concerned with software development
(and yet found the time to fill in our survey - thank you!).
(and yet found the time to fill in our survey - thank you <3).
Here is an overview of each center's contribution to our survey and the relative number of Helmholtz employees per center:
![Fig 1. Center distribution]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig1-center-distribution.svg)
![Fig 2. Domain distribution]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig2-domain-distribution.svg)
![Fig 1. Survey outreach]({{ site.directory.images | relative_url }}/posts/2021-01-15-hifis-survey-results-community/survey-outreach.svg)
We reached most Helmholtz centers except for two and received responses from each of the six main research domains.
Compared to their relative size in terms of headcount, some centers contributed over-proportionately to
the HIFIS survey. Well done, DKFZ!
As we can, we reached most Helmholtz centers except for two and received responses from each of the six main research domains.
Compared to their relative headcount, some centers contributed over-proportionately to the HIFIS survey.
Well done, DKFZ!
### Software made by Helmholtz
Now, let's have a look who stands behind the excellent software solutions made by Helmholtz:
Software is typically developed in a team with 2-5 other developers for a user base of 2-10 persons.
The median software developer in our survey has 8 years of research experience, 9 years of software development experience,
......@@ -47,30 +47,24 @@ spends 49.5% of the working time on software development, and uses 3 different p
mostly Python (76.7%), C++ (45.6%), or R (28.3%) - for details see
this [blog post on programming languages](https://software.hifis.net/report/2020/11/27/survey-results-language-vcs).
These results support what has been suspected earlier, namely, that software development is fundamental to researchers' work.
The following figure illustrates how closely research and software development are indeed related:
Indeed, the more time survey participants spent on research related work, the more experienced they were in terms of software development
as shown by the figure below.
![Fig 3. Software development vs. research experience]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig3-sw-dev-vs-research.svg)
![Fig 2. Research, software and support]({{ site.directory.images | relative_url }}/posts/2021-01-15-hifis-survey-results-community/research-software-support.svg)
The more time survey participants spent on research related work, the more experienced they were in terms of software development.
The question which role software development plays in research could then be answered: an important one!
### Current support
Given the strong link between software development and research, we wanted to know whether researchers felt sufficiently
supported at their research centers regarding software development and training.
The answer was a classical Jein. While half (50.8%) of the respondents seemed satisfied with the current state,
the other half of the respondents (49.2%) reported that they needed more support.
the other half of the respondents (49.2%) reported that they needed more support.
Clearly, we wanted to know which kind of support they needed. So we asked them.
To find out which support activities they were most interested in and which services we should focus on in the future,
we let them choose from a list of predefined services.
![Fig 4. Support satisfaction]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig4-support-satisfaction.svg)
![Fig 5. Support activities]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig5-support-activities.svg)
In order to get a more detailed picture of what could be improved, we also included a few open response questions asking
In order to get a more complete picture of what could be improved, we also included a few open response questions asking
respondents about their wishes and suggestions for a good software development support and their preferred kind of learning.
Word and code frequency analysis gave a fairly clear picture of the respondents' needs:
![Fig 6. Word and code cloud]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig6-word-and-code-cloud.svg)
![Fig 3. More than words]({{ site.directory.images | relative_url }}/posts/2021-01-15-hifis-survey-results-community/word-code-cloud.svg)
As expected, basic and advanced training courses, consulting offerings, in particular on software licensing,
and a central, easily accessible infrastructure, were at the top of the wish list.
......@@ -87,7 +81,7 @@ In particular from a community perspective, it is important to have a closer loo
of sustainable software development are already established in the Helmholtz Association.
Our survey included questions about sharing and publishing own software as well as referencing software in publications.
![Fig 7. Status quo of sustainable software development]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig7-sustainable-sw-dev.svg)
![Fig 4. Sustainable software practices]({{ site.directory.images | relative_url }}/posts/2021-01-15-hifis-survey-results-community/sustainable-software-practices.svg)
Results show that most respondents share their code regularly with the own research group,
sometimes with the research organization and research community but never with the general public.
......@@ -106,4 +100,5 @@ Visibility of research software and reproducibility of results ok but increase i
In conclusion, we can say that in addition to providing training and infrastructure, HIFIS software services
raising the awareness for and
which enable the collaboration between institutes, centers and research communities in the first place.
An always remember: Sharing is caring!
\ No newline at end of file
Sharing is caring!
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment