List view
The FishSET GUI has so much flexibility built in (including many features not necessarily required for discrete choice models) that usability suffers. FishSET Lite will be a simplified and more streamlined GUI experience that reduces flexibility but boosts usability. We are not creating a whole new shiny app, instead we will prune and reorganize the existing GUI. The pruned/reorganized version of the app will be FishSET Lite, and the "console" version will have the full flexibility for more experienced R users.
No due date•17/23 issues closedAdd more location choice models to FishSET and more policy scenarios (e.g., seasonal closures). Also, add options for biological linkages (e.g., fishing-the-line due to spillover, seasonal closures, climate related species /effort shift).
Due by December 31, 2025•1/7 issues closedMake the FishSET shiny app easier to use. This includes issues related to layout of interactive buttons, adding information widgets, add options to upload files of various formats, add error checks/messages, add status updates on functions, etc. This milestone also relates to the aesthetics of the shiny app. FishSET should look modern and updated.
Due by December 31, 2025•26/64 issues closedThe scallop vignettes will demonstrate the full flexibility of FishSET "console" functions. We may need to breakup the scallop vignettes into more chunks to make it more manageable for users. For now the plan will be to: 1. Update the scallop-mod-example with the full capabilities of the modeling functions. 2. Create a scallop-policy-example to demonstrate policy simulations using the console functions. 3. Review scallop-example vignette and update if needed. ~Clean up the code for the scallop vignette (e.g., remove any unnecessary variables from the primary data file). Also, develop a walkthrough of the scallop vignette in shiny.~
Overdue by 2 month(s)•Due by May 30, 2025•2/4 issues closedMethodically assess code to identify potential bugs, increase code quality, minimize code redundancy, optimize slow functions, and improve documentation. Steps for code review: 1. Review the design: determine whether the suggested solution is consistent with the rest of application design and architecture. 2. Check correctness: ensure the code functions as expected and achieves the intended goal. This includes adding automated tests and/or manually testing code. 3. Review code style and standards: The code should follow style and standards of the team. Code style consistency makes the code easier to read and understand. This will also help future developers. 4. Check for code smells: Smells can indicate more serious issues in the code. Large classes or methods, redundant code, excessive complexity are examples. 5. Examine readability: Code should be easy to read and understand. Good code should be self-explanatory and have sufficient annotation. 6. Evaluate performance: Assess performance issues using profile/benchmarks. Identify processing bottlenecks and improve code efficiency.
Due by December 31, 2025•1/11 issues closed