Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cannot disable verbose output on HPC - maybe use if (missing(verbose)) instead?

Open Beginner friendly
#105 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
r
Domain
backend

Research direction

Start by reading the verbose handling at the linked locations in R/runSimulation.R and R/runArraySimulation.R. Check how the default interacts with an explicitly supplied verbose = FALSE, and compare the two alternatives suggested in the issue. Done means callers can suppress this output explicitly while the default behavior remains appropriate for HPC runs.

Written by the indexing model from the issue text.

Description

Hi, I started to get check errors when I run reverse dependency checks on an HPC environment.

I'm using [runSimulation(..., verbose = FALSE)](https://github.com/futureverse/progressify/blob/c643ed257ace0875eb987555441c7f43a35309ab/inst/testme/test-progressify-SimDesign.R#L24-L26) in my checks, by verbose = FALSE` is ignored by SimDesign 2.27.

I tracked it down to:

https://github.com/philchalmers/SimDesign/blob/3842b17d9acb79d3449384c906dc8023d33eba5b/R/runSimulation.R#L1180

https://github.com/philchalmers/SimDesign/blob/3842b17d9acb79d3449384c906dc8023d33eba5b/R/runArraySimulation.R#L320

Right now I cannot disable such output without hiding certain env vars from SimDesign.

Maybe an alternative approach would be to use:

if(missing(verbose)) verbose <- on_HPC.cluster() 

Or, setting the default argument to verbose = interactive() || on_HPC.cluster()?

Dominant language
R
Stars
65
Forks
25
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from philchalmers/SimDesign

All issues in philchalmers/SimDesign

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.