Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactored and integrated Grey Wolf Optimizer #121

Open
wants to merge 18 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions python/ngen_cal/changelog.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
# V 0.3.X
- `ngen.cal` subpackage for `optmizers`
- `ngen.cal.optmizers` Grey Wolf Optimizer added

# V 0.2.1
- `ngen.cal` `Objective` enum now properly subclasses `str`. This fixes
pydantic models' json schemas that use `Objective` as a field type. See #31
Expand Down
1 change: 1 addition & 0 deletions python/ngen_cal/setup.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ install_requires =
hydrotools.metrics
hydrotools.nwis_client
pyarrow
pyswarms
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have to do this here, but we should move deps like pyswarms to an [options.extras_require]. This would let people install ngen.cal[particalswarm] for example. So, just pull in what you need.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add pyswarms to requirements.txt?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah? I am inclined to remove the root repo requirements.txt in favor of a ns package level requirements.txt instead. In either case, we should use pip freeze to generate requirements.txt instead of just listing out all the deps.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets open this as a TODO in an issue and cycle back to this.

tables
hypy @ git+https://github.com/noaa-owp/hypy@master#egg=hypy&subdirectory=python
ngen_config @ git+https://github.com/noaa-owp/ngen-cal@master#egg=ngen_config&subdirectory=python/ngen_conf
Expand Down
Empty file.
Loading
Loading