R good first issues

This issue requires updating the import statement for the PVomega library. The package name has recently changed from 'pvOmega' to 'PVomega', and the code needs to reflect this new dependency name.

The rOpenSci project is seeking new maintainers for a package, potentially a team. Interested individuals are encouraged to comment on the issue or email the provided address. The issue provides several links to resources detailing the responsibilities and process of package maintenance within the rOpenSci ecosystem.

This issue proposes establishing clear ETL conventions for the LOCATION_HISTORY table, which stores patient address history and is crucial for the OHDSI GIS toolchain. It seeks to define how to handle missing or incomplete address data, including backfilling strategies for entirely missing history, partially missing past history, and gaps within existing history.

This issue proposes to update and expand an existing guide on regulatory agency submission standards for 'xpts'. The goal is to provide more current and accurate information by verifying existing facts with accessible documentation and finding new, relevant resources like regulatory documents, conference papers, and webinars.

This issue requests an enhancement to the `parallelly::availableCores()` function to support a wider range of resource and workload managers. The goal is to detect and utilize core counts specified by environment variables from systems like PBS, PBSPro, Slurm, and Oracle Grid Engine, in addition to existing methods.

This issue proposes adding support for multi-node jobs to the `availableWorkers()` function within the `parallelly` R package when using HTCondor. Currently, it only accounts for workers on the current node, not the total allocated for a multi-node job. The maintainers are seeking users with access to multi-node HTCondor environments to help test and implement this feature.

This issue requests a review and enhancement of the tests for the `xportr_format()` function. The function validates SAS format strings against various clinical trial submission standards. The goal is to ensure existing tests cover all validation checks and verbose modes, and to identify and address any untested edge cases.

The default workflow and vignette for the 'aftables' package are missing new arguments for generating workbook properties. This leads to an irrelevant warning in the vignette and prevents users from seeing the new feature. Updating these examples will showcase the workbook properties functionality.

This issue requests the creation of a new vignette for the `mmrm` R package. The vignette should demonstrate a practical application of the package and specifically showcase the usage of the `emmeans` function, going beyond what is currently presented in the introductory vignette.

This issue proposes adding cumulative distribution function (CDF), inverse CDF (quantile), and random number generation (RNG) functions for all families currently handled by the `mgcv` package. The goal is to integrate this functionality into a new `mgcvUtils` package for enhanced diagnostics and data simulation capabilities, leveraging existing packages like `tweedie`, `distributional`, and `distributions3`.

This issue proposes the implementation of the skewed t-distribution within the brms R package. This distribution is valuable for modeling data that exhibits both skewness and heavy tails (outliers), combining the strengths of skew-normal and Student's t-distributions. The user has provided a relevant research paper outlining an MLE/EM approach but lacks the Stan programming expertise to implement it directly.

This issue is an announcement seeking new maintainers for a package within the rOpenSci organization. Interested individuals are encouraged to comment on the issue or email a provided address. Several links to documentation are provided for those interested in learning more about the role and responsibilities of a package maintainer.

A bug has been reported where markers (specifically `geom_text` labels) are appearing slightly off-center, too far down, following changes in a previous pull request (#58). The issue is noted to be similar to the default behavior of `geom_text` and might be related to complex calculations, with a suggestion that it may not be worth fixing and could be left to user adjustment.

The user is asking for clarification on how to handle subsetting of multiscale Zarr arrays, specifically when the desired subset indices do not align perfectly across all resolution levels. They are proposing potential solutions like restricting to valid indices, dropping incompatible low-resolution scales, or allowing user control over this behavior.

This issue proposes improving code coverage for API testing by exploring methods to avoid sharing private information. Potential solutions include using a fake free user account or leveraging the {vcr} library, though some functionalities might require paid accounts.

The current `togglr` package lacks a way to retrieve all workspace IDs for a user. The `get_workspace_id()` function only fetches the first workspace, which might not be the default. The issue proposes adding functionality to query all workspace IDs, potentially by modifying `get_workspace_id()` with a `default_workspace` argument, though this could make the function name misleading.

This issue requests the addition of numerous missing primitive functions and API endpoints to the {anvl} package. The goal is to fill gaps that currently prevent the package from being used for practical problems, covering areas like reverse rules, general tensor operations, statistical distributions, and linear algebra.

The `devtools::check()` function is generating a NOTE because of a stray file named 'NULL' within the R CMD check directory. The task is to identify the source of this file and prevent its creation. This is a maintenance chore that affects both the main branch and feature branches.

The `rglobi` R package was archived on CRAN due to a 'donttest' violation related to its handling of internet resources. Despite passing all tests at the time of archiving, CRAN policy requires packages using internet resources to fail gracefully with informative messages if the resource is unavailable or changed. The maintainer needs to address this policy violation to reinstate the package.

This issue reports a potential token leak within the echarts4r GitHub repository. The provided link points to a GitHub Actions run that likely encountered the leak, suggesting a security vulnerability that needs immediate investigation and remediation.

The `export_abnFit` example in the `abn` package fails because the data is lazy-loaded, causing `data(ex1.dag.data)` to produce an error. The issue suggests adapting the error message in `abn-internal.R` and highlights a mismatch between the number of distributions defined and the data columns.

The user is encountering an error during BIOMOD_Projection where the environmental levels in the new projection data do not match those used during model training. Specifically, the `geo.sgmc` layer in the projection data is missing levels 14 and 16, which were present in the original environmental data used for modeling. The user is seeking advice on how to resolve this discrepancy, considering options like modifying the projection data to include NA for missing levels.

The current maintainer of the MODIStsp R package is seeking a co-maintainer or new maintainer due to a career change. The package is stable, and the primary tasks involve assisting users, managing potential USGS server changes, and updating for new MODIS products. This is a call for help to ensure the continued support of the package.

This issue is a call for new maintainers for a software package. Interested individuals are encouraged to comment on the issue or email a provided address. Links to relevant documentation about package maintenance are also included.

This issue proposes making the examples for the `export_design_to_excel()` function runnable. Currently, the examples are enclosed in `\dontrun{}` and rely on an undefined variable, preventing them from being tested by `R CMD check`. The suggested solution involves defining a sample design and exporting it to a temporary file, ensuring the examples can be executed safely and quickly.

The user is encountering an error when trying to download CSV data or generate other visualizations (Tree, Network, Heatmap) after performing an ssGSEA analysis with a custom GMT file. The error message indicates a site unavailability for downloads and a general error for other visualizations, suggesting a backend or data processing issue.

This issue highlights an inconsistency between the Slurm resource name used internally by the `getClusters` function ('cluster') and the name referenced in the documentation ('clusters'). This discrepancy can lead to unexpected behavior, such as jobs not being correctly identified, causing user confusion and potential debugging difficulties.

This issue highlights inconsistencies in the capitalization of function argument descriptions within the documentation. The author suggests standardizing these descriptions, likely by adhering to a specific convention file, to improve clarity and maintainability.

This issue proposes refactoring the code by updating the '{tern}' function. The goal is to eliminate the need for a separate function called 's_proportion_diff_j', suggesting that the functionality can be integrated into '{tern}'. This is likely a code cleanup and simplification task.

This issue proposes replacing the current ad-hoc method of generating random seeds for jobs with a more robust approach using L'Cuyer RNG streams from the `parallel` package. The current method of `seed + job.id` might lead to suboptimal or correlated random numbers. The suggested L'Cuyer approach ensures better randomness and allows for nested seed generation, with a fallback option for user-defined seed functions if direct implementation is not immediately feasible.