Missing files about poker_ml HOT 6 CLOSED

This line checks if that file exists, and if not, it will generate it and save:

It takes a bit of time to generate it, and I did not want to submit it into git as it is about 100MB in size.

from poker_ml.

Oh, also update the path to match your env. :) I should have fixed to make that path relative, but never got to it.

from poker_ml.

This line checks if that file exists, and if not, it will generate it and save:

poker_ml/expected_value/src/main.rs

Line 1066 in 60d75e1

if Path::new(&combinations_path).exists() {

It takes a bit of time to generate it, and I did not want to submit it into git as it is about 100MB in size.

I did change the paths so that all the paths match my working directory in main.rs but the files never got generated

Is it the cargo build --release step that generates these files?

from poker_ml.

Oh, that's odd. I guess for some reason that check returns that file exists?
You can try to add output to see what that exists() function returns.

cargo build --release creates executable in release configuration. you need to run cargo run to run the executable, or you can just manually execute the binary as well.

from poker_ml.

Oh, that's odd. I guess for some reason that check returns that file exists? You can try to add output to see what that exists() function returns.

cargo build --release creates executable in release configuration. you need to run cargo run to run the executable, or you can just manually execute the binary as well.

Turns out that I mistyped my directories. This step seems to be fine now. However I suggest adding in the instructions to run the command cargo update -p lexical-core If running a newer version of rust. That’s what I had to do to get cargo build —release to work

from poker_ml.

Oh, that's odd. I guess for some reason that check returns that file exists? You can try to add output to see what that exists() function returns.
cargo build --release creates executable in release configuration. you need to run cargo run to run the executable, or you can just manually execute the binary as well.

Turns out that I mistyped my directories. This step seems to be fine now. However I suggest adding in the instructions to run the command cargo update -p lexical-core If running a newer version of rust. That’s what I had to do to get cargo build —release to work

Ok, I realized I needed to install nvidia environment for docker, so this part is okay now. Thanks!

from poker_ml.