libamtrack / web Goto Github PK

What do you think to instant open data series values when only one:
I think about skipping modal window at first print screen and only show this one at the second one

Right now user sees a mix of plotting ("multiple") and calculating ("single") functions.
This is a bit misleading and not what user expects at first glance.

What do you think of grouping them (i.e. on main page) in two separate groups ?
One would be "plot" for example on the top of the page and another one would be "calculate" and seen in the bottom of the page (probably much less used).

There could be also another solution if you have some.

Main reason behind that is to be more clean on the presentation level.

To reproduce go to:
https://libamtrack.github.io/web/#StoppingPower/Massstoppingpower

Axis scales are log-log

Before clicking on "Submit" click button Plot as "Line".

Axis are changing to lin-lin - why ?

Right now files with data ("Download" option) are bit tricky to digest:

I propose to:

• remove #haha line
• add comment line mentioning that the file was generated with libamtrack
• add comment line with the time the file was generated
• strip " from fields with numerical data: 0.1,0.014651766707559846 instead of "0.1","0.014651766707559846"

What do you think of saving multiple series in many-columns format, instead of appending the data below ?

https://marwin1991.github.io/cToJsFunctionsGenerator/

"Points" is an improper naming.

On the page https://libamtrackweb.readthedocs.io/en/latest/add_function.html I find the information:

Prepare special JavaScript wrapper function to use compiled from C library function. Use JSFunctionGenerator to quickly get wrapper method from C function’s signature.

Where should I put the autogenerate JS file ?

46.44 MeV would be much clearer than 46.444113823764 MeV

when material other than liquid water is choosen

There is a problem with deploying app after changes was made in script.

Link to travis build.

Page looks ugly on mobile browsers

I had some problems with setting correct values for functions that I added in #74. I tried to find them directly in library repository but it was very difficult. Could you @grzanka specify values or ranges which will be appropriate for that functions?

I especially mean function CSDA Energy After Slab but for all this functions when you insert incorrect parameters the application will crash. Error messages appearing in browser console aren't very helpful:

Here is a very dirty list of tasks and things to correct, quickly written in the plane. Feel free to migrate them to separate issues

1. METHODS TO IMPLEMENT

• range (AT_CSDA_range_g_cm2_multi / AT_CSDA_range_g_cm2_single)
• energy after slab (AT_CSDA_energy_after_slab_E_MeV_u_single / AT_CSDA_energy_after_slab_E_MeV_u_multi)

2. PROBLEMS

Beta From Energy Single

• Setting Energy to 0,1 (or some string) gives error "MESSAGE TO DEVELOPER: NO PARAMETER E_MeV_u IN OBJECT PASSED TO THIS FUNCTIONS" it is very misleading, same for negative numbers.
• TODO: add Energy units there
• I wouldn't expect that users will type energy from range outside [1e-3, 1e3] thus printing 4 digits after . should be enough
• Setting energy to 0 should give beta=0, it gives an error now.
• Setting energy to negative number gives white page.

Beta From Energy

• By default we should have energy range 0..300 and 300 points instead of step.
• Switching from "Line" to "Points" should not generate new line serie.

"Energy From Beta Single"

• setting Beta to 1 gives white page.
• Displaing 3 significat digits should be enough

"Energy From Beta"

• start point at 0 should be allowed, by default we should have 300 points for beta between 0 and 0.8
• On horizonta axis energy units should be displayed.

"Energy Of Particle With Given Momentum Single"

• default momentum should be 300

"Energy Of Particle With Given Momentum"

• start 0, end 500, 500 points

"Relativistic Momentum Per Nucleon Of Particle Single"

• default energy: 150

"Relativistic Momentum Per Nucleon Of Particle"

• should allow start at 0, end should be 300, and 300 points,

"Relativistic Momentum Per Nucleon Of Particle":

• start at 0.001, end at 10 MeV, plot as Line
• 500 points forming "geometrical" ! series
• by default log scale on X and Y axis

"Maximum Electron Range Single"

• by default energy 0.01 MeV
• output units should be m, not MeV - to check

"Mass stopping power with no"

• start at 0.01, end at 500 MeV
• 500 points forming "geometrical" ! series
• by default log scale on X and Y axis
• default source: PSTAR

"Effective Charge From Beta Barkas-Bethe Single"

• by default: carbon ion

• beta 0.1

• no output units

  "Effective Charge From Beta Barkas-Bethe"

• by default proton

• start at 0, end at 0.6, 500 points forming geometrical series

  • by default logarithmic scale on X, linear scale on Y

    "Effective Charge From Energy Barkas-Bethe Single"

  • energy: 10

  • particle: C

  • no output units

  • energy units: "MeV/amu"

    "Effective Charge From Beta Barkas-Bethe"

  • start 0.01, end 100, 500 points forming geometrical series

  • no output units

  • by default logarithmic scale on X, linear scale on Y

  • energy units: "MeV/amu", not "MeV"

Many configuration files have validators for input.

1. Can we provide value like 10e10 or maybe 10^10 ?
2. Some cases should not have limit? Like energy can be infinity, but we know that numbers in computers cant. Will it cause overflow?( i will create new issue to investigate it ). So i was wondering about validator like: >0, so it accept everything greater than 0.

I think is not important issue, but leave it for future.

It would be nice (although with low priority) a "status message", i.e. in the header, with the information about date of deployment to GH pages and commit hash. Small font, just for debugging.

Check from where the differences comes from: core libamtrack library or from some GUI features.

Investigate overflows in compiled functions.

optionally generate .wasm file with travis

Old browsers like IE or old chrome versions do not have build support for WASM, we should display some warning or info to user about it. #62

Now Physics Routines is the biggest category, maybe we ca split it in two or thre subcategories?

When plotting mass stopping power I'd like to have:

• by default logarithmic scale on X and Y axis
• energy range 0.1 .... 500 MeV
• PSTAR source
• energy (X data points) forming geometrical serie from 0.1 ... 500 MeV and having ~500 points

This would probably require setting some default parameters in javascript code

This would probably require a bit of javascript coding

We need to find a solution to problem with functions that have parameters which are dependent each other.

For example:
RDD Model defines number of allowed RDD Model Parameters

https://docs.travis-ci.com/user/deployment/pages/

Also require a bit more of Javascript coding

Currently there is only default plotly.js name "trace X", where "X" is number from 0 to ...

Show alert when trying to run big task for large arrasy biger than 100k
use "-s ALLOW_MEMORY_GROWTH=1" during compilation to JS/WASM

For CSDA Range when we choose particles and materials from end of the list, application has problem with memory. @marwin1991, probably we should compile library with flag allowing to expand memory size in runtime?

This problem is related with #76.

On left side - log scale, right - linear.

I leave it here because it is interesting topic.

Please investigate https://libamtrack.github.io/web/#TrackStructure/RadialDoseDistribution ?

It looks that all the needed numbers are in the JSON file, but still this is not reflected in UI:

• default log-log plot

In the input form start and end fields are visible, but there is no label mentioning which physical quantity do they represent