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

use generation_node_name on the GeneratorRun #2003

Closed
wants to merge 5 commits into from

Conversation

mgarrard
Copy link
Contributor

Summary: Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Nov 18, 2023
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51432075

mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 27, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51432075

mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 28, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51432075

mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 28, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51432075

mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 28, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51432075

Mia Garrard added 5 commits November 28, 2023 12:00
…ethod on GenerationNode (facebook#2018)

Summary:

This diff does the following:
Replaces the `get_generator_run_limit()` method on GenerationStep with `generator_run_limit` on GenerationNode. The new method relies on transition criterion to determine the number of generator runs, and only checks criterion that are trial based. I actually think this may not need to be expanded because the trial based criterion seem the most related to new generator run creation, but it could be expanded easily in the future if a usecase requires doing so.

upcoming:
(0) Finish removing GenerationStep methods in
(1) delete functions from GenStep that aren't needed anymore
(2) update the storage to include nodes independently (and not just as part of step)
(3) final pass on all the doc strings
(4) add transition criterion to the repr string + some of the other fields that havent made it yet on GeneratinoNode
(5) Do a final pass of the generationStrategy/GenerationNode files to see what else can be migrated/condensed
(6) rename transiton criterion to action criterion

Reviewed By: lena-kashtelyan

Differential Revision: D51169425
…ategy (facebook#2002)

Summary:

This diff removes the last uses of num_remaining_trials_until_max_parallelism(), num_trials, num_can_complete, and enforce_num_trials from the GenerationStrategy file. This can be done bc we can compute all the necessary info on GenerationNode now. And, since we want GenerationStrategy to accept GenerationNodes and GenerationSteps we cannot have any leftover calls from the GenerationStep level.

Reviewed By: lena-kashtelyan

Differential Revision: D51172395
Summary:

This method is redundant and checks for a state that we should never reach. In the process of updating to GenerationNode based GS, maintaining this method would entail keeping track of previous nodes. The tech debt of doing so outweighs the potential reward of keeping the function. Also I think since use_update has been deprecated this function is also less relevant.

Reviewed By: lena-kashtelyan

Differential Revision: D51420534
Summary:

We want to use the GenerationNode equivalent of model which is fitted_model instead of the GenerationStep field model

Reviewed By: lena-kashtelyan

Differential Revision: D51431892
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D51432075

mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 29, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 29, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
mgarrard pushed a commit to mgarrard/Ax that referenced this pull request Nov 29, 2023
Summary:

Replace the use of generation_step_index with generation_node_name because GenerationStrategy should no longer access index

Differential Revision: D51432075
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in b56610f.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity. fb-exported Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants