Skip to content

Feature(#401): set seed for short term trend estimation - #470

Closed
atyrell3 wants to merge 10 commits into
devfrom
feature/i401-set-seed
Closed

atyrell3 wants to merge 10 commits into
devfrom
feature/i401-set-seed

Conversation

@atyrell3

@atyrell3 atyrell3 commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

UNDER REVIEW. DO NOT MERGE!!!

Justification

Short term trend plotting was not reproducible last year, resulting in trend lines appearing/disappearing when plots were regenerated. This is caused by the bootstrapping in the arfit methods used to fit the short-term trend.

Fixes #401

Types of changes

  • Fix (non-breaking change which fixes a bug)
  • Feature (non-breaking change which adds or changes functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Other change (if none of the other choices apply)

Reviewer instructions

  • Reinstall package
  • Run the same ecodata::plot_** call with n = 10 multiple times to ensure short-term trend (or lack thereof) is reproducible. Suggest to use plot_comdat(varName = "revenue", n = 10) as this gave us trouble last year.

Formatting

This repo contains an air.toml file that automatically formats code to a set of standards.
It is preferred that contributors and reviewers install the Air formatting tool.
Code submitted in this pull request will be automatically checked for correct formatting.

andybeet and others added 10 commits September 11, 2024 14:25
pull plot_thermal_habitat_persistence fix into main
correction to the formatting of a landing page table
Sync `dev` and `main` branches
Update DESCRIPTION and NEWS.md files to reflect new version for release
Sync `dev` and `master`
…s a bootstrap method, this ensures that plots will be reproducible
@atyrell3
atyrell3 requested review from BBeltz1 and andybeet October 7, 2026 15:49
@andybeet andybeet linked an issue Oct 7, 2026 that may be closed by this pull request
@andybeet andybeet changed the title Feature/i401 set seed Feature(#401): set seed for short term trend estimation Oct 7, 2026
@andybeet

andybeet commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

This all looks fine, but when i try switch to this branch, Rstudio wont let me and puts in a state where i am in "no branch" and when i try to switch back to dev i get fatal: not a git repository (or any of the parent directories): .git. and i am stuck! I think i need to reclone?

Not sure why this is happening, since the diff (from dev) is only one line in one file. However I am guessing this might be due to the fact this branch was a couple of years old and something funky happened when updating to dev? Anyone else having an issue like this? or is it just me?

EDIT: Ah, i see. It was due to an old branch. The .Rproj has been untracked in earlier PRs and this PR removed it. Had to create a new project in existing directory, then all was good.

@BBeltz1
BBeltz1 marked this pull request as draft October 7, 2026 16:40
@BBeltz1

BBeltz1 commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

This all looks fine, but when i try switch to this branch, Rstudio wont let me and puts in a state where i am in "no branch" and when i try to switch back to dev i get fatal: not a git repository (or any of the parent directories): .git. and i am stuck! I think i need to reclone?

Not sure why this is happening, since the diff (from dev) is only one line in one file. However I am guessing this might be due to the fact this branch was a couple of years old and something funky happened when updating to dev? Anyone else having an issue like this? or is it just me?

EDIT: Ah, i see. It was due to an old branch. The .Rproj has been untracked in earlier PRs and this PR removed it. Had to create a new project in existing directory, then all was good.

Not quite. This PR is problematic. I've converted to a draft for now. Please suspend any actions until further notice. Thanks!

@atyrell3

atyrell3 commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

I cloned off of main this morning and updated the 1 file, not sure what is going on with the old pull requests and .Rproj

@BBeltz1

BBeltz1 commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

I cloned off of main this morning and updated the 1 file, not sure what is going on with the old pull requests and .Rproj

Yes, this is what's causing the problems. A branch cloned from main cannot be merged into dev.

@atyrell3

atyrell3 commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

do you want me to open another pr with a different branch?

@BBeltz1

BBeltz1 commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

I cloned off of main this morning and updated the 1 file, not sure what is going on with the old pull requests and .Rproj

Yes, this is what's causing the problems. A branch cloned from main cannot be merged into dev.

You'll need to branch off of dev, make the change again and then create a new PR merging from the new feature branch to dev.

@atyrell3 atyrell3 closed this Oct 7, 2026
@atyrell3
atyrell3 deleted the feature/i401-set-seed branch October 7, 2026 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add set.seed within short-term trend fitting

3 participants