numeric

numeric copied to clipboard

Last commit is back to 2012.

it seems like

I emailed the repo owner not too long ago and he seems to be relatively busy, though interested in people still submitting patches. He also mentioned that the library goes through a very particular test system before any revision, which is why it wasn't so easy for him to be able to keep up with it.

Anyways, that's about all I have in terms of this. I would be interested in working on the convex solver for a similar library, if anyone is willing to either fork this project for a full active branch, or start a new project.

Yeah, it really concerns me that basic issues such as #66 have not be resolved. He may be interested in people submitting patches, but he has not accepted any it seems.

I don't believe that it is. Someone who has time should fork it and take over maintanence.

On Thu, Jun 9, 2016 at 11:17 AM, Aaron Gokaslan [email protected] wrote:

Yeah, it really concerns me that basic issues such as #66 https://github.com/sloisel/numeric/pull/66 have not be resolved. He may be interested in people submitting patches, but he has not accepted any it seems.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sloisel/numeric/issues/72#issuecomment-224946828, or mute the thread https://github.com/notifications/unsubscribe/ABXuOlELp4Kf5-K3FdiCEqtuvfm10Ni4ks5qKDysgaJpZM4HfRQk .

Yeah I just emailed the repo owner to ask if he'd be willing to add a collaborator to the repository to help with merging commits.

I'd be willing to help out with maintanence to some degree. I'm somewhat busy for the next few months but could chip in.

On Thu, Jun 9, 2016 at 12:46 PM, Aaron Gokaslan [email protected] wrote:

Yeah I just emailed the repo owner to ask if he'd be willing to add a collaborator to the repository to help with merging commits.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/sloisel/numeric/issues/72#issuecomment-224972721, or mute the thread https://github.com/notifications/unsubscribe/ABXuOpVqaMfPu73oB6pyFwu70X1zC4i5ks5qKFGLgaJpZM4HfRQk .

If anyone is still up for forking the project and continuing a main development branch, I'd still be interested in some work on the general optimization solvers and such.

Okay, I've waited two weeks and haven't received a response. It might just be easiest if we get an official fork going. Anyone else in seeing an updated v2 version of this repo?

Yeah, I don't think there's an updated version with any major revisions, to be honest, just a bunch of pull requests/small patches. So, go ahead and fork it, I think we'd all be on board with it and just start contributing.

I think the project should be maintained and improved in some way. I am also intereseted in and can help as much i can. The framework(a numeric enviroment) i work on highly depend on numeric.js

Okay, so, could somebody who is willing to be active on the project just branch it such that we can all contribute?

I can do that :+1:

https://github.com/peoplewareDo/numeric

Send you patches and let works on it

I was waiting for the repo owner to respond by the end of the week, but I suppose this could work too. Shouldn't we do a "hard" fork instead of a soft fork though? I know my behavior is just click through to the original repo on soft-fork. Also maybe we should list it under a Github organization for organization's sake in case this ever happens again?

Also, we probably want to rebrand it to note that behavior might significantly diverge from the original such as numeric2.js.

I put it under an Organization so, just send the patch with the rebrand to the new repo. Let's work.

I still think it should be a hard fork though, instead of being a soft fork on Github. Not sure how to convert it without deleting the repo though. (The way to do a hard fork is to clone the repo, then change the repo remote location and push it to the new location, that way it makes a full copy of the git history instead of doing whatever wizardy deduplication stuff Github is doing behind the scenes.

PS: Add me to the organization.

Yeah, that sounds good... I think the author wouldn't mind too much and worst comes to worst, we could just consolidate with the author at the end.

P.S. It would be great if I could also be added to the Organization.

Hi,

Of course you guys can fork if you want!

The main problem that I have is that, whenever I make a change, I must run the entire test suite in a variety of browsers. I've set it up on my mac to run in Chrome, Firefox, as well as on IE in a Windows Parallels machine; to me this seemed like the minimal coverage necessary. I have found that testing on all browsers is very important because there's often something that will fail in only one of them.

To do this, I use Selenium, and this is where it gets hairy. Every time I want to release, I invariably have to update Selenium and all plugins, across two operating systems, and also often I have to upgrade my scripts that do the communication between mac and Windows for this testing.

I only release when all the tests are green. It should look like this: http://www.numericjs.com/report.html

Fancy people with money have "continuous deployment" or whatever, a farm of servers that automatically test in a variety of browsers, but I don't have this and I don't want to sysadmin it either!

Sauce labs if free for open source projects, could look into that. https://saucelabs.com/opensauce/

@sloisel if that is the problem, you could also check https://ci.testling.com/

I am doing a refactoring of this project recently. ( https://github.com/timqian/mathlab ) The aims includes:

1. Make the pointwise functions also suitable for Complex and Sparse matrix.
2. Not using function constructor to generate functions
3. Separate the package into small files so that people can require functions only when they need.
4. Unit test using mocha
5. Rename the T to Complex and {x: ..., y: ...} to {re: ..., im:...}
6. Make sparse matrix to be an Constructor
7. add more functions
8. ...

Please let me know your thoughts about it.

Yes, you can configure Sauce labs for automatic GitHub integrated CI testing on real browsers. Each pull request could then be automatically checked against a test suite. So you would not have to run anything locally. It is free for open source projects.

@timqian Once you get the CI testing/refactoring done and such, I'd be happy to contribute to debugging some of the optimization methods.

@mitar Want to help setup the integrated CI testing on the peopledoware fork? I want to get the automated testing setup on at least one fork so we can get the benchmarking setup on at least one fork.

Anyone forking numericjs should work from Daniel Holden's fork ( @orangeduck ), which added NumPy-style broadcasting and other useful stuff. He did good work. He even updated the documentation page.

Here is his repository: https://github.com/orangeduck/numeric

Here is his pull request: https://github.com/sloisel/numeric/pull/56

Here is his announcement on the Google Group: https://groups.google.com/forum/#!topic/numericjs/giRexhL3ydg

I made #76 with Travis CI tests.

You can see example run here: https://travis-ci.org/mitar/numeric/builds/180668112

@sloisel: Do you care giving commit bits to few people here? I think there are quite few who would be willing to help maintain it.

Now we test on multiple node version using Travis CI, and on Firefox and Chrome using Circle CI, and IE using Circle CI + Sauce Labs. See example: https://circleci.com/gh/mitar/numeric/17

@sloisel may I advise that you set up a Patreon project for this? I'm sure the people here who make money from this project will be happy to contribute.