rosegpe / roselapweb Goto Github PK

We should use C instead

Plots don't take up the full screen width, and they also are too tall.

This is unneccessary, pls use all screen real estate

It is kinda a pain in the ass scrolling to the bottom to add a new batch

at all

In the large engine sim testing 10+ different engines, I would like the best time for score calculation to be the best time for a tested configuration.

like you cant actually do anything

How we'd like this to work:

Consider studies with the transmission. Right now we sweep across final drive ratio in many cases simply because we want to find the final drive ratio that best suits the transmission. We don't actually care about the rest of the data (except maybe for sensitivity- this may warrant another line graph for optimal points). We just want to optimize with respect to an axis.

This would free us up to do more complex things, like a 2D study between transmission spread and shift time that held gear ratio 'optimal'.

The spec would be like adding another axis to the plot, but maybe instead denote it as axis_optimizer.

The label (A) should completely ovverride the labels on this axis

see bottom row

The y-axis here is goofy and uses full floating point precision on one of the datapoints rather than rounding.

you say "save and run"
it puts an entry in for "queing" with yours
it puts an entry in that is actually running for "EngineSim - Michigan - Simplified"

I did some digging and what's going on is an SQL query returns the same batch config ID (one corresponding to an instance of "EngineSim - Michigan - Simplified")

I would like to be able to make small changes in my program and review both options. Currently, I need to copy paste into a new document.

2018-07-16 20:31:54,520 | ERROR : Traceback (most recent call last):
File "c:/wamp/www/RoseLap/py/RoseLapCore/webrunner.py", line 76, in
results = batcher.batch(tests, vehicle, tracks, model, out[1] != 0)
File "c:\wamp\www\RoseLap\py\RoseLapCore\batcher.py", line 21, in batch
batch["track_data"] = batch_run(flatTargets, permutations, batch["test_vals"], vehicle, tracks, model, include_output)
File "c:\wamp\www\RoseLap\py\RoseLapCore\batcher.py", line 173, in batch_run
segments = track_segmentation.file_to_segments(fn, dl, opts=opts)
File "c:\wamp\www\RoseLap\py\RoseLapCore\input_processing\track_segmentation.py", line 388, in file_to_segments
pts,sectors = points_in_each_seg_slow(testpath, dl, plot, opts)
File "c:\wamp\www\RoseLap\py\RoseLapCore\input_processing\track_segmentation.py", line 174, in points_in_each_seg_slow
spl = UnivariateSpline(l, k, k=smoothing_dof)
File "C:\Python27\lib\site-packages\scipy\interpolate\fitpack2.py", line 185, in init
xb=bbox[0],xe=bbox[1],s=s)
MemoryError
Traceback (most recent call last):
File "c:/wamp/www/RoseLap/py/RoseLapCore/webrunner.py", line 76, in
results = batcher.batch(tests, vehicle, tracks, model, out[1] != 0)
File "c:\wamp\www\RoseLap\py\RoseLapCore\batcher.py", line 21, in batch
batch["track_data"] = batch_run(flatTargets, permutations, batch["test_vals"], vehicle, tracks, model, include_output)
File "c:\wamp\www\RoseLap\py\RoseLapCore\batcher.py", line 173, in batch_run
segments = track_segmentation.file_to_segments(fn, dl, opts=opts)
File "c:\wamp\www\RoseLap\py\RoseLapCore\input_processing\track_segmentation.py", line 388, in file_to_segments
pts,sectors = points_in_each_seg_slow(testpath, dl, plot, opts)
File "c:\wamp\www\RoseLap\py\RoseLapCore\input_processing\track_segmentation.py", line 174, in points_in_each_seg_slow
spl = UnivariateSpline(l, k, k=smoothing_dof)
File "C:\Python27\lib\site-packages\scipy\interpolate\fitpack2.py", line 185, in init
xb=bbox[0],xe=bbox[1],s=s)
MemoryError

When there's lots of fails it's really annoying

If you save and run and it runs immediately, the submit time is wrong

Decrease user error and frustration from dealing with YAML and decrease time training people to use YAML

Oops.

only occurs on COMPENSATOR, never remotely

Not that big of an issue, it just kinda annoys me.

damnit andrew

we don't have a fair assessment of skidpad points rn

Right now you can literally create an account and cause havoc even if we fix SQL stuff

This is a simple fix with the yavascript

Ran a simple 2D study for just skidpad / accel and it should be done by now but it's still 'In Progress.'

Is there feedback to say 'you wrote correct YAML'? Can we pipe error messages to the web? Anything is good- we are dealing with engineers, not the least common denominator of society; give us data.

delet this

Whitespace is bad and the plot is also crammed

I expected this to function as a 'save as'.