Tarcísio Fischer
Tarcísio Fischer
@tcanabrava Are you interested in making the PR for this? If not or if you don't respond in the following days, I'll be happy to do it.
AFAIR, it was because we only used for floats... Feel free to add it, though. Sounds like a good idea to me
Perhaps this can be solved by using the new `NDArraysRegressionFixture`? @tovrstra What do you think?
> Any particular reason why the scientific notation is not used? 'e' I don't remember :( Possibly it was truncating values? Really don't know. @tadeu @arthursoprana maybe you remember? Anyway,...
> @tarcisiofischer the fix, changing to what @arthursoprana posted, fixes my issues. Awesome! :D Could you please open an MR with this plus a test? (Test could do exactly what...
Well, if that's the feeling I think you may just create some tests for the other issues and drop the idea of keeping the data types. I still think this...
I'm unsure. (a) Someone saves pd.DataFrame({'col_1': [1.0, 2.0, 3.0], }) those are meant to be floats. (b) Someone loads it again. Since this PR is not merged, they are now...
As I said, I won't oppose. Just for the record, this _may_ be an example of a corner case (I may be wrong, I did it quick just to check):...
@darioizzo **I didn't make the `pso_gen` modifications yet** because I wanted to show the `pso` version first, so you can validate if everything is as expected in terms of project...
> @tarcisiofischer thanks for the PR! > > It's a +1 from me on the coding side, I'll let @darioizzo review the algorithmic part. Nice thanks @bluescarni :) > This...