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

Adapt notebooks to mlpack 4 API #208

Merged
merged 5 commits into from
Oct 24, 2022
Merged

Conversation

rcurtin
Copy link
Member

@rcurtin rcurtin commented Oct 14, 2022

I went through all of the C++ notebooks and made changes that reflect the latest changes in mlpack master (which will be mlpack 4). Basically these changes are:

I also made a few fixes where necessary, and sometimes I reduced the computational complexity of the models we were learning so we would stay within resource limits.

Now, every notebook runs successfully on Binder, with two exceptions:

  • The reinforcement learning notebooks. I didn't touch those.
  • The cifar10_eval notebook needs an 8GB binder instance to succeed. I had one of those once, when starting a notebook on Binder, but then I started getting 2GB instances. However, it should work.

After merging this PR, https://datasets.mlpack.org/cifarNet2.xml will need to be moved to https://datasets.mlpack.org/cifarNet.xml.

There is one additional issue: datasets.mlpack.org is not available from OVH binder instances. I'm trying to work with the Binder Gitter chat and Github repository to get a resolution there.

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@github-actions
Copy link

Binder 👈 Launch a binder notebook on branch rcurtin/examples/binder-mlpack4

]
},
{
"cell_type": "code",
"execution_count": 22,
"id": "97fdc354-57d0-4e28-91e8-1d707fc24226",
"metadata": {},
"outputs": [],
"outputs": [
Copy link
Member

Choose a reason for hiding this comment

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

I guess, we got lucky before.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah. I suppose we could increase the penalty to work around the issue, but I don't think it's a big deal either way.

Copy link
Member

Choose a reason for hiding this comment

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

The results are pretty much the same, so I don't think this is needed.

Copy link
Member

@zoq zoq left a comment

Choose a reason for hiding this comment

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

Looks good to me, no comments from my side.

Copy link

@mlpack-bot mlpack-bot bot left a comment

Choose a reason for hiding this comment

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

Second approval provided automatically after 24 hours. 👍

@rcurtin rcurtin merged commit 4f0453b into mlpack:master Oct 24, 2022
@rcurtin rcurtin deleted the binder-mlpack4 branch October 24, 2022 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants