Hi Colin, I really like this and would like to use it for making a s

Hello, and thanks for writing! There's a thing called <a href="http:

I love it, a java library with fortran style :-D

here's why I prefer fortran before java: I use the following:<

<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" da

Simple in browser use?,about littleredcomputer/odex-js

Comments (11)

littleredcomputer commented on June 8, 2024 1

Hello, and thanks for writing!

There's a thing called browserify which prepares JS modules written in the node style for the browser. The source code that drives my github pages is on github too, so you can take a peek at how I did it here, using gulp to orchestrate the typescript compilation and browserify steps.

Warning: on the frontend, I'm a dabbler not an expert, so you might find a way to put it together that you like better. For example, other ways to do this include requirejs and webpack

from odex-js.

zahachtah commented on June 8, 2024

Hi, and thanks for those pointers. I'll see how far I get, I'll let you know :-)

from odex-js.

zahachtah commented on June 8, 2024

I am getting slowly somewhere...

to get an array output of the integration, does this seem like a reasonable (efficient) way or can I get it to store an array of outputs directly, e.g. in out.y (now out.y seems to be the last value only)?:

a=[];
s.denseOutput = true;
out=s.solve(f, 0, [1], 1, s.grid(0.2, function(x,y) {
  a.push(y[0]);
}));

from odex-js.

littleredcomputer commented on June 8, 2024

Odex has a very Fortran style, so there is no dynamic memory allocation in it, and the array storage that it statically allocates is often recycled. Your solution is what I would write.

from odex-js.

zahachtah commented on June 8, 2024

I love it, a javascript library with fortran style :-D

from odex-js.

littleredcomputer commented on June 8, 2024

Heh. Here's the source if you're curious. Initially, I tried to change the style, but that turned into a fight. In the end, I decided that the original style has virtues of its own (discretion is the better part of valor).

For example, if you don't need to store the whole vector of results because you are plotting them as they are generated, you don't have to. So it's a feature :)

from odex-js.

zahachtah commented on June 8, 2024

here's why I prefer fortran before javascript:

I use the following:

var f = function(x, y) {
  return y;
};
data=[];
s.denseOutput = true;
out=s.solve(f, 0, [1], 1, s.grid(0.2, function(x,y) {
  data.push(y[0]);
}));

and data becomes a nice array one can pass to a graphing script,

BUT...change only a little:

var f = function(x, y) {
  return 0.1 * y;
};

and data returns only a single value.....and there's no logic why this happens.

Will have to sleep on this :-)

from odex-js.

littleredcomputer commented on June 8, 2024

var f = function(x, y) {
  return [0.1 * y[0]];
}

y is always an array even when solving a one-dimensional system. The job of f is to return a vector of the same length as y.

from odex-js.

zahachtah commented on June 8, 2024

thanks. working now

from odex-js.

bramvandijk88 commented on June 8, 2024

I'm trying to use Browserify to make your package available within the browser too, but so far I have failed doing so. Could you maybe give an example as to how you would do this? I've gone all the way with your examples on github, but it really doesn't allow me to do what I want to do:

Load up your module
Load up my own code
Call Solver() from my own code in the browser

Thanks for the help :)

<html>
    <head><title>Some ODE integration </title></head>
    <!--<script type="module" src="./odex.js"></script>-->
            <script type="module" src="some_ode_thing.js"></script>
    <body>
    </body>
</html>

With some_ode_thing.js being:

import {Solver, Derivative} from './odex.js'

var s = new Solver(2);
var eq = function(x, y) {
    return [y[1], -y[0]];
};
// This is y'' = -y, y(0) = 1, y'(0) = 0, e.g. cos(x)
console.log(s.solve(eq, 0, [1, 0], Math.PI));
// We observe that at x = π, y is near -1 and y' is near 0,
// as expected.

As discussed above, this won't work in the browser, although running a nodejs version (with require) works perfectly fine:

user@computer$ node lotka_volterra.js 
{ y: [ -1.0000012130554767, 2.867958371527322e-7 ],
  outcome: 0,
  nStep: 8,
  xEnd: 3.141592653589793,
  nAccept: 8,
  nReject: 0,
  nEval: 114 }

I tried to use browserify, but didn't get really far.

[Resolved]

Alright, I found a way of doing it, i was just browserifying the wrong way. For future troubleshooters: here's what to do with the above code to run it in the browser:

browserify some_ode_thing.js -o out.js

And then run out.js within your html code.

from odex-js.

littleredcomputer commented on June 8, 2024

I forgot how to use Browserify, but I recently set up something like this with webpack. I did it by following the instructions here <https://webpack.js.org/guides/getting-started/>. My src/index.js has this in it: import {Solver, Outcome} from 'odex' let s = new Solver(6); s.denseOutput = true; s.solve( ... My dist/index.html looks like this: <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>Getting Started</title> </head> <body> <script src="main.js"></script> </body> </html> And here's package.json: { "name": "foo", "version": "1.0.0", "description": "", "private": true, "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "keywords": [], "author": "", "license": "ISC", "devDependencies": { "webpack": "^5.5.0", "webpack-cli": "^4.2.0" }, "dependencies": { "odex": "^2.0.4" } } I just run "npx webpack" to build "main.js", which rewrites all the import/export stuff to work in the browser. HTH!

…

On Fri, Nov 20, 2020 at 1:59 AM Bram van Dijk ***@***.***> wrote: I'm trying to use Browserify to make your package available within the browser too, but so far I have failed doing so. Could you maybe give an example as to how you would do this? I've gone all the way with your examples on github, but it really doesn't allow me to do what I want to do: Load up your module Load up my own code Call Solver() from my own code in the browser Thanks for the help :) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB3Y7NIUGYVSNUHWQVZHXDSQY4WJANCNFSM4DMB2TZA> .

from odex-js.

Simple in browser use? about odex-js HOT 11 CLOSED

Comments (11)

Related Issues (2)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs