Github5561: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
No edit summary
Line 11: Line 11:


= Research write-up =
= Research write-up =
== Summary ==
We carried out research with GR users to learn how they dealt with issues arising from the following use-cases:
1. opening a .grc file created with an older version of GNU Radio, in a newer version.
2.  opening a .grc file created with a newer version of GNU Radio, in an older version.
We wanted to learn about the following:
1. if they had issues with either of these scenarios happened to them, and if so asked them to describe the situation
2. the most common causes
3. the troubleshooting routes they took
4. how they fixed the issue

Revision as of 08:54, 4 May 2022

#5561. When a .grc file behaves differently due to being opened on different GRC version

This work is related to Github Issue 5561.

1. Do research with community to understand what they do when this happens currently. I've put together a short survey to ask users for their experience of this situation, what behaviour was caused, how they dealt with it. Based on the results of that research we create some notifications with advice on how to deal with it. 2. Analysis of the survey quantitative data being done using a collaborative online whiteboard called Miro. You're welcome to leave comments on the Miro board. 3. Write the draft support documentation. Send it to the UX group and to the mailing list for contributions or comments. 4. Do UX design for notification.

Research write-up

Summary

We carried out research with GR users to learn how they dealt with issues arising from the following use-cases:

1. opening a .grc file created with an older version of GNU Radio, in a newer version. 2. opening a .grc file created with a newer version of GNU Radio, in an older version.

We wanted to learn about the following:

1. if they had issues with either of these scenarios happened to them, and if so asked them to describe the situation 2. the most common causes 3. the troubleshooting routes they took 4. how they fixed the issue