<akhunti1[m]>
[microservice/mlpack-3.1.1/build/include/mlpack/prereqs.hpp:74:10: fatal error: boost/serialization/serialization.hpp: No such file or directory
<EshaanAgarwal[m]>
jonpsy[m]: in HER i am storing all the transitions in a vector
<jonpsy[m]>
share me the type of transition
<jonpsy[m]>
what exactly is `transition`
<EshaanAgarwal[m]>
jonpsy[m]: its a struct of state next state isEnd goal etc
<EshaanAgarwal[m]>
i have solved it. I actually passed the arguments in wrong order
<EshaanAgarwal[m]>
just got a new one 🫠 Let me look at that one
<jonpsy[m]>
haha, send that pastebin then
<jonpsy[m]>
basically your constructor was failing
<jonpsy[m]>
for `transition`
<EshaanAgarwal[m]>
jonpsy[m]: nope i was pushing back the tuple of transition in wrong order. For ex {nextState, state} or {state, nextState}
<EshaanAgarwal[m]>
jonpsy[m]: yup one minute
<EshaanAgarwal[m]>
EshaanAgarwal[m]: looks like i managed that one too. Phew
<jonpsy[m]>
EshaanAgarwal[m]: yes, which is why it couldn't "construct" your object during `push_back`. Since the real ctor expected a different order of inputs
<EshaanAgarwal[m]>
EshaanAgarwal[m]: test got compiled successfully finally.
<EshaanAgarwal[m]>
jonpsy[m]: yup you are right
<jonpsy[m]>
onwards to testing them, do it rn. LEmme know th results
<EshaanAgarwal[m]>
jonpsy[m]: yes ! just doing it in a minute. Will keep you posted
<jonpsy[m]>
For adding to testsuite, bitflipping is fine. But for actually checking its workin, we need to go for a beter env.
<EshaanAgarwal[m]>
jonpsy[m]: sure ! what do you propose for that ?
<EshaanAgarwal[m]>
jonpsy[m]: Not much. I have heard about the debugger though
<jonpsy[m]>
EshaanAgarwal[m]: How have you been debugging till now?
<EshaanAgarwal[m]>
jonpsy[m]: I have set a private variable called length for the length of binary vector
<EshaanAgarwal[m]>
jonpsy[m]: Pretty much without that 😅
<jonpsy[m]>
how exactly?
<jonpsy[m]>
VSC right?
<EshaanAgarwal[m]>
jonpsy[m]: Yes
<jonpsy[m]>
you do realize VSC uses GDB internally?
<EshaanAgarwal[m]>
jonpsy[m]: I did not know
<jonpsy[m]>
I mean it just gives you in a prettier format, bt that doens't change the fact
<jonpsy[m]>
basially a wrapper around gdb
<EshaanAgarwal[m]>
jonpsy[m]: Ok ! I actually did not face much issues related to matrices. In the PPO one we used the C++ program and printed everything
<EshaanAgarwal[m]>
Coming back to the issue. I am not sure if I get the issue correctly ? I do understand it's related to the dimension and length
<jonpsy[m]>
that error was runtime, i presume?
<EshaanAgarwal[m]>
jonpsy[m]: Yeah I ran the test
<jonpsy[m]>
ofc, so when its matrix multiplying. The end and start dimension should match
<EshaanAgarwal[m]>
jonpsy[m]: Yes !
<jonpsy[m]>
not all the test in that file. Just this single test
<EshaanAgarwal[m]>
<jonpsy[m]> "> <@jonpsy:matrix.org> sent an..." <- So I change this variable right ?
<jonpsy[m]>
can you run `BitFlippingWithNStepHindsightDQN` just this test
<EshaanAgarwal[m]>
jonpsy[m]: I ran only this and just gave you the error I got
<jonpsy[m]>
yh
<jonpsy[m]>
EshaanAgarwal[m]: uh, so it should be 10 ig?
<jonpsy[m]>
try replacin with 10 and re-runnin
<EshaanAgarwal[m]>
jonpsy[m]: But we are making it a variable right ?
<EshaanAgarwal[m]>
jonpsy[m]: Ok ! Give me a minute
<jonpsy[m]>
so?
<EshaanAgarwal[m]>
jonpsy[m]: It's compiling ! Taking a little bit time.
<EshaanAgarwal[m]>
yup looks like issue with buffer size. justa a hunch
<EshaanAgarwal[m]>
jonpsy[m]: yup ! i will see what i can dig till then
<jonpsy[m]>
That's fine, but we should never get `segmentation faults` . Once you find your error, put appropriate `asserts` so that its caught in compile time
<EshaanAgarwal[m]>
jonpsy[m]: understood
<jonpsy[m]>
can't stress the "never" enough. It creates bad image
<EshaanAgarwal[m]>
jonpsy[m]: i understand 😢
<EshaanAgarwal[m]>
will look in it then ! will post if i get something
<akhunti1[m]>
Hi rcurtin this is my cmakelist.txt file . i added boost library inside my project folder. but still i am getting [ Could NOT find Boost (missing: Boost_INCLUDE_DIR serialization] this error.
<akhunti1[m]>
As our project already build in mlpack 3.1.1., so it is very difficult for us to go for newer version of mlpack.
<rcurtin[m]>
I think most things are reverse compatible from 3.4.2 to 3.1.1, so it may be easier than you think to upgrade, but okay
<rcurtin[m]>
if CMake is not finding Boost successfully, make sure it's installed on the machine, and if you installed it to a custom directory you might try specifying the `BOOST_ROOT` option to CMake