Skip to content

Excluding Big files from Machine Learning samples #958

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

Open
PatriceDargenton opened this issue Jun 24, 2022 · 0 comments
Open

Excluding Big files from Machine Learning samples #958

PatriceDargenton opened this issue Jun 24, 2022 · 0 comments

Comments

@PatriceDargenton
Copy link

In order to reduce Machine Learning samples zip size (from more than 2 Gb to 87 Mb), just commit this Pull Request:

#949

I added also a VB branch with many samples, taken from this repository and updated:

https://github.com/Nukepayload2/machinelearning-samples/tree/master/samples/visualbasic

In the VB branch I included functional tests to download all datasets, and to test all samples, in one click!

I think it is still possible to commit first the C# and F# sample repository, and then after to update Nukepayload2 VB repository and commit the VB branch to the Nukepayload2 VB repository, via a second Pull Request.

I failed to compile this demo (30/87 Mb), I think packages can be downloaded too, like other samples:
csharp\end-to-end-apps\Unity-HelloMLNET\HelloMLNET

This one compile but does not work:
csharp\getting-started\DeepLearning_ImageClassification_Binary

I did not test these demos:
csharp\end-to-end-apps\Scalable*

All other demos work fine (C#, F# and VB).
All packages are up to date (F# and VB).

Why committing directly to the master branch? At first I wanted to be able to check the size of the repository at each step, but finally, I only checked the size of the downloaded zip (It's almost impossible to delete a large file or a sensitive file from a repository, without causing an inextricable mess, especially for forked repositories), but I probably could have made a branch indeed.

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

No branches or pull requests

1 participant