Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shiny Interface #33

Closed
10 tasks done
tofof opened this issue Feb 4, 2023 · 7 comments
Closed
10 tasks done

Shiny Interface #33

tofof opened this issue Feb 4, 2023 · 7 comments
Assignees

Comments

@tofof
Copy link
Collaborator

tofof commented Feb 4, 2023

Use the Shiny framework to create the main interface for undergraduates to use for data entry.

  • Refactor main to reduce reliance on globals
  • Validate inputs and input agreement prior to doing expensive import process.
  • Display graphs and offer space for annotation
    • Weight Graph
    • Secondary Graph
      • Rxn Graph
      • Ben wanted .. some other option
      • Other alternative for when Rxn vs dB doesn't make sense due to only 1 intensity
  • Commit data to archives only after user has verified accuracy
  • Reset workflow while preserving username
@nohelix
Copy link
Collaborator

nohelix commented Feb 11, 2023

I am getting an error on the graphs of:
Warning in grid.Call(C_textBounds, as.graphicsAnnot(x$label), x$x, x$y, :
font family not found in Windows font database

@tofof
Copy link
Collaborator Author

tofof commented Feb 11, 2023

See admin tools/font setup.R

@tofof tofof self-assigned this Feb 14, 2023
@tofof tofof linked a pull request Feb 15, 2023 that will close this issue
@nohelix nohelix added enhancement New feature or request priority: in progress labels Feb 17, 2023
@nohelix
Copy link
Collaborator

nohelix commented Feb 25, 2023

I am getting an error on the graphs of: Warning in grid.Call(C_textBounds, as.graphicsAnnot(x$label), x$x, x$y, : font family not found in Windows font database

Fixed and run on all work station computers. It required the complete setup ☹️

@nohelix
Copy link
Collaborator

nohelix commented Feb 25, 2023

Ben wanted .. some other option
Other alternative for when Rxn vs dB doesn't make sense due to only 1 intensity

Other option was a Hit% graph. For discussion on graphing improvements, see issue #45

@nohelix nohelix mentioned this issue Mar 7, 2023
nohelix added a commit that referenced this issue Mar 10, 2023
Better labeling both in location and now ID dashed line. Maybe should be folded in to #45 in prep for #33.
@nohelix
Copy link
Collaborator

nohelix commented Mar 10, 2023

Would it be possible to capture the console messages (i.e. the write lines, etc) to a log file?

It seems like sink would allow this.

nohelix added a commit that referenced this issue Mar 15, 2023
This adds flexability for the future and fills the roll of the old FA_detailed.

It holds hits_detailed for graphing (see #49) which can be used in #33.

Prior to deployment, the old run_archive needs to be modified to match this format.
@tofof
Copy link
Collaborator Author

tofof commented Apr 4, 2023

Ready for deployment.

@tofof
Copy link
Collaborator Author

tofof commented Apr 12, 2023

Closed by #56

@tofof tofof closed this as completed Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants