V1.0 prep

[wincowgerDEV]

@zsteinmetz, creating this PR so that we can have everything in one place. Below I am bringing over comments and check boxes from the other 3 PRs and assigning each of us to tasks. Would it be alright if I merge all these to V1.0 prep?

Package Down Documentation (@wincowgerDEV) #126

• Update SOP with new functionality and explanations.
• Update homepage.
• Customize the website to look its best.
• Set URL address to something like OpenSpecy.org.

Functions for managing spectra for v1.0 (@zsteinmetz) #125

• finalize functions to align and concatenate spectra required by Reading functions for v1.0 #124
• add test routines
• update docs
• check if everything works as expected

Reading functions for v1.0 (@zsteinmetz) #124

• functions to align and concatenate spectra required before multiple spectra could be read at once, e.g. from a zip file
• finalize reading functions
• add test routines and update sample files
• update docs
• check if everything works as expected

Functions to be renamed/changed (@zsteinmetz)

• sample.OpenSpecy() -> sample_spec()
• correlate_spectra() -> cor_spec()
• collapse_spectra() -> collapse_spec()
• process_spectra() -> process_spec()
• identify_spectra() -> ident_spec()
• characterize_particles() -> def_features()
• heatmap_OpenSpecy() -> heatmap_spec()
• plot_OpenSpecy() -> plotly_spec()
• to_hyperSpec() -> as_hyperSpec()
• subtr_bg() -> subtr_baseline()
• replace magrittr pipe %>% with native R pipe |> were possible
• replace object argument with x where possible
• update run_app()

General checks and CRAN compliance (@zsteinmetz)

• passing urlchecker::url_check()
• passing GitHub checks
• passing devtools::check(remote = TRUE, manual = TRUE)
• passing devtools::check_win_devel()
• optimizing/adding tests (still missing for read_envi and read_envi_nic)
• check docs for consistency and spelling mistakes
• finalize dependencies in DESCRIPTION
• update NEWS.md
• update cran-comments.md

[wincowgerDEV]

Checking all these R files for completion and tests:

• adj_intens
• as_OpenSpecy
• collapse_particles
• conform_spec
• data_norm
• flatten_range
• gen_OpenSpecy
• human_ts
• io_spec
• manage_lib
• manage_spec
• OpenSpecy-package
• plots_reports
• process_spectra
• raman_hdpe
• read_envi
• read_envi_nic
• read_ext
• read_multi
• read_opus_raw
• read_opus
• restric_range
• share_spec
• signal_noise
• smooth_intens
• spec_res
• subtr_bg
• test_lib
• zzz
• match_spec

[zsteinmetz]

@wincowgerDEV What do you think when we might be ready to merge into main? I am asking because I actually don't like to see the main branch fail. Currently it's only because of that GitHub Action deprecation but still. If we need more time here, no problem. Then I just cherry pick the GitHub Action commits and merge them already before merging the whole thing. If it's only documentation left, I guess we could merge this one here already and continue working on the SOP on this or another branch.

[zsteinmetz]

@wincowgerDEV I just split up the SOP vignette into three separate ones: the main SOP, the advanced spec part, and the SpectraGryph stuff. The idea behind was (1) to improve clarity also with respect to packagedown and (2) to be more flexible which vignettes to exclude for the CRAN package to keep the file size down. For now, I only added the main SOP to be submitted to CRAN excluding the two other ones that only go to packagedown. What do you think? I can revert it if it doesn't make sense to you, of course.

[wincowgerDEV]

@wincowgerDEV What do you think when we might be ready to merge into main? I am asking because I actually don't like to see the main branch fail. Currently it's only because of that GitHub Action deprecation but still. If we need more time here, no problem. Then I just cherry pick the GitHub Action commits and merge them already before merging the whole thing. If it's only documentation left, I guess we could merge this one here already and continue working on the SOP on this or another branch.

I think we merge with main asap 🙂. Just vignettes left. I'm gonna finish the vignettes today. Love what you did with the split too, that's super handy. There will likely still be some small bugs to shake out but the community can help us find them more easily once it is in main. You wanna do the honors of merging?

[zsteinmetz]

Sure! I'm going to merge as soon as all checks have passed.

We could even think about splitting the package and app parts in the current SOP vignette. This would make the actual package vignette super small, because we don't need all the screenshots, and would give us more space for sample files and so on. The app vignette could then go to packagedown only.

[wincowgerDEV]

That's not a bad idea. Was going back and forth about whether to do that. I think we originally kept them together so that the app could expedite the learning process for the package but I totally get that now we have a lot more app features and those each have images and that can make a big file size for the package. Maybe in the app vignette and the package vignette we try to maintain the same headings to make it easy to search between the two?

…

On Wed, Aug 30, 2023, 7:52 AM Zacharias Steinmetz ***@***.***> wrote: Sure! I'm going to merge as soon as all checks have passed. We could even think about splitting the package and app parts in the current SOP vignette. This would make the actual package vignette super small, because we don't need all the screenshots, and would give us more space for sample files and so on. The app vignette could then go to packagedown only. — Reply to this email directly, view it on GitHub <#129 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGMUJU22YOK2OQ36FAE5K4DXX5HRPANCNFSM6AAAAAA2C62GJI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zsteinmetz]

Maybe in the app vignette and the package vignette we try to maintain the same headings to make it easy to search between the two?

Sounds good! We could also reference the package functions in the app vignette and vice versa.

[wincowgerDEV]

Yeah that's true, maybe even add a link to the header on the other package vignette too! I like keeping the package as small as possible, there may come a time we want to make another big push in a few years and we will want the space for test files or porting over other people's 1000 line codes 😂.

…

On Wed, Aug 30, 2023, 8:00 AM Zacharias Steinmetz ***@***.***> wrote: Maybe in the app vignette and the package vignette we try to maintain the same headings to make it easy to search between the two? Sounds good! We could also reference the package functions in the app vignette and vice versa. — Reply to this email directly, view it on GitHub <#129 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGMUJU44YXP2Z5UONO7ZEVDXX5IRNANCNFSM6AAAAAA2C62GJI> . You are receiving this because you were mentioned.Message ID: ***@***.***>