-
Notifications
You must be signed in to change notification settings - Fork 177
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
Remove hyperparmeter tuning code #454
base: master
Are you sure you want to change the base?
Conversation
ashelkovnykov
commented
Feb 14, 2020
- Photon team at LinkedIn has continued to work on hyperparameter tuning code
- Working on releasing it as a separate open source project
- Until then, removing the old version which was available but unused
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
* @param transformMap A Map with key-value pairs of indices and names of transform functions. | ||
* @return The transformed vector. | ||
*/ | ||
def transformForward( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we delete this function? Our internal atlas-ml does not have functions to perform parameter transformation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's wait to merge this PR until the internal dependency changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yunboouyang @cmjiang
I don't understand this comment - are these two functions not available in the internal hyperparameter tuning library? Is there a blocker to copying the implementation over from here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason to leave these two functions in Photon ML is that, we wanted to do the same transformation in Photon ML. Photon ML doesn't have the dependency on the internal hyperparameter tuning library. If Photon ML doesn't need to reuse these functions, we can move it to the tuning library.
* @param transformMap A Map with key-value pairs of indices and names of transform functions. | ||
* @return The transformed vector. | ||
*/ | ||
def transformBackward( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have the same concern here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above please
* @throws IllegalAccessException | ||
*/ | ||
def apply(className: String): HyperparameterTuner[GameEstimator.GameResult] = | ||
Class.forName(className) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do users specify the class name? Do they need to specify the full class path "com.linkedin.atlas.tuner.AtlasTuner"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right - full class path.
.../src/main/scala/com/linkedin/photon/ml/io/scopt/game/ScoptGameTrainingParametersParser.scala
Outdated
Show resolved
Hide resolved
- Photon team at LinkedIn has continued to work on hyperparameter tuning code - Working on releasing it as a separate open source project - Until then, removing the old version which was available but unused
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM