Maintenance notification: GitLab and all corresponding services will be down for maintenance from Thursday, June 24th 16:00 until Friday, June 25th 08:00. Please excuse the inconvenience and plan your work accordingly.

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

Add word cloud plot

parent 46950fc1
......@@ -29,15 +29,13 @@ With about 42.000 employees within Helmholtz we can say that at least 1% are con
(and care about empirical social research).
Here is an overview of each center's contribution to our survey and the relative number of Helmholtz employees per center:
# FIG1: Center distribution
{:.treat-as-figure}
![Fig 1: Center distribution]({{ site.directory.images | relative_url }}/posts/2020-12-23-hifis-survey-results-community/center-distribution.svg)
![Fig 1. Center distribution]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig1-center-distribution.svg)
Well done, DKFZ!
We received responses from each of the six main research domains:
![Fig 2: Domain distribution]({{ site.directory.images | relative_url }}/posts/2020-12-23-hifis-survey-results-community/domain-distribution.svg)
![Fig 2. Domain distribution]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig2-domain-distribution.svg)
Now, let's have a look who stands behind the groundbreaking software solutions made by Helmholtz:
The median software developer in our survey has 8 years of research experience, 9 years of software development experience,
......@@ -48,27 +46,27 @@ Software is typically developed in a team with 2-5 other developers for a user b
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 related:
![Fig 3: Software development vs. research experience]({{ site.directory.images | relative_url }}/posts/2020-12-23-hifis-survey-results-community/swdev-vs-research.svg)
![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)
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!
Given the strong link between software development and research, we wanted to know whether researchers felt sufficiently supported at their centers.
Given the strong link between software development and research, we wanted to know whether researchers felt sufficiently supported at their research centers.
![Fig 4: Support satisfaction]({{ site.directory.images | relative_url }}/posts/2020-12-23-hifis-survey-results-community/support.svg)
![Fig 4. Support satisfaction]({{ site.directory.images | relative_url }}/posts/2021-01-08-hifis-survey-results-community/fig4-support-satisfaction.svg)
The answer was a classical Jein. While half (50.8%) of the respondents seemed satisfied with the status quo,
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.
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 5: Support activities]({{ site.directory.images | relative_url }}/posts/2020-12-23-hifis-survey-results-community/support-activities.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
respondents about their wishes and suggestions for a good software development support and their
preferred kind of learning. Word frequency analysis + code frequency analysis
![Fig 6: Word and code cloud]({{ site.directory.images | relative_url }}/posts/2020-12-23-hifis-survey-results-community/clouds.svg)
![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)
This suggests that in addition to training and consulting offerings a central, easily accessible infrastructure is urgently needed.
Another aspect is the recognition and regulation of open science practices and open source development.
......@@ -79,10 +77,12 @@ in particular from a community perspective, important to have a closer look at t
Our survey included questions about sharing and publishing own software as well as referencing software in publications.
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.
They publish their code regularly on internal platforms or public code sharing platforms like GitHub but never on a research repository or a software package index.
Code comments, README files and installation instrucions are regularly provided by most respondents, user manuals, requirement specification and technical doucmentation sometimes,
Code comments, README files and installation instrucions are regularly provided by most respondents, user manuals, requirement specification and technical documentation sometimes,
while release notes, contributor guides and developer guides are almost never provided.
While this suggests that there is at least , it is surprising that most respondents do not license their code
![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)
Visibility of research software and reproducibility of results ok but increase in reusability
In conclusion we can say that in addition to providing training and infrastructure, HIFIS software services
\ No newline at end of file
This source diff could not be displayed because it is too large. You can view the blob instead.
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