Stats
-
Not really coding, but SW or package selection....
let's say you have a Java application and you need to integrate some statistical capabilities - nothing fancy, basic regression-level stuff, Q-Q plots...
and you know better than to roll your own.and the customer would prefer something we know is correctly implementedR is
thean obvious way to go... but going OSS is tricky from the client's infrastructure side (ie we have no control of the servers... and R does not yet have approval) ...Any thoughts?
Paging @boomzilla, @accalia, @dkf, @Mikael_Svahnberg as my last, best hope.
-
I have never needed to do such a thing. I'm guessing that nothing is approved so far by the client?
Some stuff here:
I'm assuming that you could include any jar in your application. My first stop would probably be Apache Commons Math (also mentioned at the above link), though I've never used it personally:
-
let's say you have a Java application and you need to integrate some statistical capabilities
... hmm. i havent touched Java since 1.5.....
but what you want is something similar to servercooties.com or @shadowmod? take data about what's going on and turn it into pretty graphs (that still have useful info) for management?
-
take data about what's going on and turn it into pretty graphs (that still have useful info) for management?
A bit more statistical, but more or less...
-
A bit more statistical, but more or less...
i'll have a poke around and see what i can find.
-
going OSS is tricky from the client's infrastructure side
Open source Java library
I'm sensing a problem here...
-
I'm sensing a problem here...
I'm assuming he integrates it into his program, not some dependency that the customer has to install somewhere inside their infrastructure. I'm assuming this is similar to my customer, where we can do pretty much whatever inside our application, but installing other stuff outside of that requires approval.
-
That makes sense. I was assuming more like a license that's incompatible with GPL or something.
Sorry for the derail, @ijij. I can't offer anything constructive since my Java experience consists of a couple of barebones Android apps
-
Sorry for the derail, @ijij. I can't offer anything constructive since my Java experience consists of a couple of barebones Android apps
It's all useful... we (work) are discussing "approaches" so its all good to hear about.
BRB - well, meeting, so not right back...
-
Well. I do believe that would accomplish great swaths of what we need to do.
Not completely plug-n-play, but I need a job too.
Thanks!
Now, to figure out the licensing piece....
-
Sorry, as a university, we usually do not worry too much about licenses and such. Therfore, I'd go with R. I googled a bit and found a java implementation of R, that ought to be embeddable as a jar-file:
They ask you to contact them for a commercial alternative, but the github repo is GPL 3.0. Don't know how they manage to combine those two...
-
They ask you to contact them for a commercial alternative, but the github repo is GPL 3.0. Don't know how they manage to combine those two...
If it's their copyright, they can offer whatever licenses they want. So you can go with the GPL3 and abide by those terms or keep all your proprietary stuff proprietary by paying them for the privilege of using their software. Seems reasonable to me.
-
It looks like there would be a couple of ways of using R....
When I posted, I was narrowly focused on one thing, but you've reminded me to rethink a second area where R would be the better route - if the functionality actually is a requirement.
PS why are you even here at this hour?? But, thanks! ;)
-
One thing with R and licenses, though. Most of the interesting stuff goes on in packages, and these may have other licenses. They are at least not necessarily covered by the deal you strike with the supplier of R.
-
I've used jasper reports. They do have a few chart types, but I don't think its exactly what you're looking for.
-
One thing with R and licenses, though. Most of the interesting stuff goes on in packages, and these may have other licenses. They are at least not necessarily covered by the deal you strike with the supplier of R.
I think we're OK on that front - we're not doing anything interesting... ;)
I'll keep that in mind though.