Shiny development about fieldhub HOT 3 CLOSED

Dear Thiago,

We have addressed all the issues included for this first version of FielDHub as per our previous communications, including some improvements on the guidelines for using complex and simple experimental designs. We also added examples of how the input files should look like. Please see example in the picture below, that shows when the user selects the option for importing the entry list, there is an automatic pop-up window that will be displayed and indicating the user how the data should be formatted, with check lines or control lines at the beginning of the entry list, followed by the experimental lines. This improvement was expanded to all experimental design options in FielDHub.

Our commitment for the next version will include a guide that will help users to navigate step by step the whole process for complex designs. For the moment there is a guide in our FieldHub website @ https://didiermurillof.github.io/FielDHub/index.html .

We look forward to hear from you.

Thank you very much for your time and consideration.

The Breeding Pipeline DB Managers @ NDSU

from fieldhub.

Dear Thiago,

Thank you for the careful review and relevant suggestions. We have put a lot of effort into these areas and appreciate the feedback. We are actively working to build more interactive guides for more complex experimental designs. We estimate that these changes will take weeks to properly design and incorporate, and we are planning to include them in the next release. As users are actively planning their experiments for 2021, we feel that FielDHub is sufficient for meeting users needs for this upcoming growing season. Delaying release will prevent some of our users from designing their experiments in FielDHub this year. While we remain focused on improving usability and will add more intuitive guides, we believe that it is helpful for users this year and we are seeking to distribute FielDHub as soon as possible. The less complex designs, such as RCBD, are the most widely used, and FielDHub is simple for those use cases. Nevertheless, we are willing to remove references to an intuitive design until we update the guides for the most complex designs if that helps us to expedite publication.

Didier, Ana & Tom

from fieldhub.

Dear Didier, Ana & Tom,

I absolutely agree with your point of view. There is no reason to barrier the publication due to small (but important) details for the first release. I agree that this suggestion will take some weeks to be included, and I am more than happy to accept the paper when other suggestions I have made were implemented in the package. We can leave this suggestion for the next release. I kindly ask you to make the next realise as soon as possible.

Is this reasonable for you?
Best wishes,

Thiago

from fieldhub.