in order to avoid problems with files being owned by root, mldb needs the mldb_data directory to be owned by the current user. You can normally fix it with
sudo chown $UID.$UID mldb_data in the current directory
Hi there!
Nice tool, I'm trying to run
After preparing images I still getting an exception during the call to
How I can filter out those images failing withoout breaking whole process? Thanks
Nice tool, I'm trying to run
KDNuggets Transfer Learning Blog Postwith my own set of images.After preparing images I still getting an exception during the call to
inception seems that one of the images fails.How I can filter out those images failing withoout breaking whole process? Thanks
You can wrap the call to inception in a
try() SQL statement. check the "Handling errors line by line" section here: https://docs.mldb.ai/doc/#builtin/sql/ValueExpression.md.html
Hello again,
So after creating that API by using my re-trained model of inception, I want to know something. Since all of the mldb functions that I used make REST calls, can I make REST calls from ubuntu shell to the local server to predict food using that jupyter script? If yes, then how can I do that?
Thanks in advance :)
So after creating that API by using my re-trained model of inception, I want to know something. Since all of the mldb functions that I used make REST calls, can I make REST calls from ubuntu shell to the local server to predict food using that jupyter script? If yes, then how can I do that?
Thanks in advance :)
I am just curious to know, since I have been getting this error when I try to start hte container: MLDB (version 2017.06.20.dev-e84f8da) is starting up
/opt/bin/mldb_runner: error while loading shared libraries: libxml++-2.6.so.2: cannot open shared object file: No such file or directory
/opt/bin/mldb_runner: error while loading shared libraries: libxml++-2.6.so.2: cannot open shared object file: No such file or directory
Perhaps I need to go into the container and fix something ?
Yeah something is definitely not right, when i git checkout v2017.01.24.0 and build MLDB, it runs with no issues: docker run --rm=true -v /home/ubuntu/mldb_data:/mldb_data -e MLDB_IDS="id" -p 8080:80 quay.io/mldb/mldb:ubuntu-HEAD-5b8653bc2828f1a89e23876e2d05c9a21dd2ed6a
MLDB (version 2017.06.20.dev-5b8653b) is starting up
reading configuration from file: '/etc/mldb.conf'
MLDB ready
Looks like, perhaps, some sort of CI needs to be set up that does a build and an initial smoke test, to make sure that the latest container actually runs
Sorry for the delay
I think the version of mldb_base we have online is too old. I'll push a new one.
(This is the base image used to build the mldb docker)
so you should run "docker pull quay.io/mldb/mldb_base:14.04" and then rebuild
Btw, I really like what I see about the MLDB.
hi @mldbai , I see you guys are all together continue working on another cool product not part of RTBkit. Our team @venediktov @abushev and @mrbald would love to learn how we could integrate your product to vanilla-rtb . Perhaps there is some room for cooperation ? You can ping us on Gitter or send email to info@forkbid.com . Best , vanilla-team.
the value could be a dataset, which can be accessed through REST or SQL queries which can conceptually pass a DAG. Is that correct?
Does MLDB SQL support inner joins?
@jeremybarnes you wrote most of it didn't you? I'd be curious, did you create a virtual machine and a custom on-disk B-tree implementation? I'm thinking of sqlite here, was that an inspiration at all
@FinchPowers Are you guys active with this ?
Do you have any improvement suggestions or do you feel it to be practicle integrating it into a DBMS?
This is a story about four people named Everybody, Somebody, Anybody and Nobody. There was an important job to be done and Everybody was sure that Somebody would do it. Anybody could have done it, but Nobody did it. Somebody got angry about that, because it was Everybody’s job. Everybody thought Anybody could do it, but Nobody realized that Everybody wouldn’t do it. It ended up that Everybody blamed Somebody when Nobody did what Anybody could have.
