Skip to content

Remove references to scipopt.org; update DoE paper reference#3968

Open
jsiirola wants to merge 4 commits into
Pyomo:mainfrom
jsiirola:scip-urls
Open

Remove references to scipopt.org; update DoE paper reference#3968
jsiirola wants to merge 4 commits into
Pyomo:mainfrom
jsiirola:scip-urls

Conversation

@jsiirola
Copy link
Copy Markdown
Member

@jsiirola jsiirola commented May 29, 2026

Fixes # .

Summary/Motivation:

The scipopt.org web server now aggressively disallows automated connections. As a result, the URL verification action is consistently failing. This PR removes all references to scipopt.org removes any "deep" references to scipopt.org (e.g., to documentation or license) from the repository and documentation.

CC (for awareness): @scipopt

While we were updating URLs, this tracks a change in the DOI link for the DoE paper, and moves the internal reference in the Pyomo docs from the bibliography to the publications list.

Changes proposed in this PR:

  • Remove all references to scipopt.org except for https://www.scipopt.org
  • Exclude https://www.scipopt.org from URL validation
  • Update DOI for the Pyomo.DOE paper
  • Move internal citation for the Pyomo.DoE paper from "bibliography" to "publications"

AI-Use Disclosure

  • AI tools were NOT used during the preparation of this PR

or

  • AI tools contributed to the development of this PR

    • AI tools generated documentation (including the PR description/comments, code comments, and/or Sphinx documentation)
    • AI tools generated tests (baselines, examples, and/or code)
    • AI tools generated code (apart from tests)

    Review process (select ONE):

    • Rewritten: All AI-generated content was rewritten by me before being committed.
    • Reviewed/verified: I retained AI-generated content and verified it before committing. Verification included (as applicable):
      • Ran the code and fixed issues
      • Added and ran tests
      • Checked correctness/logic of code and tests
      • Checked for alignment with the contribution guide
      • Considered security implications
    • As-is: AI-generated content was commited directly to the repository

Notes for reviewers (optional):

Legal Acknowledgement

By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution:

  1. I agree my contributions are submitted under the BSD license.
  2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

@jsiirola jsiirola changed the title Remove references to scipopt.org Remove references to scipopt.org; update DoE paper reference May 29, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented May 29, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.11%. Comparing base (cf43df0) to head (4a52048).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3968      +/-   ##
==========================================
- Coverage   90.11%   90.11%   -0.01%     
==========================================
  Files         909      909              
  Lines      108561   108561              
==========================================
- Hits        97835    97832       -3     
- Misses      10726    10729       +3     
Flag Coverage Δ
builders 29.11% <ø> (+<0.01%) ⬆️
default 86.11% <ø> (?)
expensive 35.12% <ø> (?)
linux 87.63% <ø> (-1.99%) ⬇️
linux_other 87.63% <ø> (ø)
oldsolvers 28.04% <ø> (+<0.01%) ⬆️
osx 83.05% <ø> (ø)
win 85.37% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

2 participants