Lima-bpm-web-server issueshttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues2023-10-31T11:26:33+01:00https://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/37High sampling rate kills UI2023-10-31T11:26:33+01:00Stuart FisherHigh sampling rate kills UIAt 10khz on id10 the bpm viewer is very slow, presumably the client is being flooded. Need to limit the framerate from server -\> client.
Dont think https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/merge_requests/32 is deployed yet...At 10khz on id10 the bpm viewer is very slow, presumably the client is being flooded. Need to limit the framerate from server -\> client.
Dont think https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/merge_requests/32 is deployed yet on ID10 so cant decouple sample rate and exposure.
cc @chushkinStuart FisherStuart Fisherhttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/36Add option to disable bpm cross2023-04-18T16:55:39+02:00Stuart FisherAdd option to disable bpm crosscc @maciej.jankowskicc @maciej.jankowskiStuart FisherStuart Fisherhttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/31Requests for improvement2022-08-10T15:32:59+02:00Nicolas Sévelin-RadiguetRequests for improvementDear maintainers,
Here are some requests for improvements for the BPM web:
1. Have the name of the BPM in the `<title>` tag of the client webpage.
- Rationale: we need to have multiple BPMs opened simultaneously and it would make sw...Dear maintainers,
Here are some requests for improvements for the BPM web:
1. Have the name of the BPM in the `<title>` tag of the client webpage.
- Rationale: we need to have multiple BPMs opened simultaneously and it would make switching from one to another much more straightforward. As of now we have multiple tabs titled "BPM Monitor".
2. Decouple "Exposure Time" and "Sampling rate"
- One is not necessarily the inverse of the other. E.g. one might want to integrate only 50μs every 10s. (and the standard Basler are 30 fps max).
- Would this also open the possibility to hard trigger the acquisition (instead of the present soft trigger)? Personally very interested for our laser applications on ID24.
3. Have a way to adjust gain, lock it
4. Have a way for the application to save all the settings and reload them when restarted (this occurs a lot! :disappointed: )
- At each restart, we have to re-set the "Exposure time" (or "Sampling rate") and any image transformations previously configured (rotate or flip).
5. Have a color image when the camera is a color one.
- We have a microscope with a large-sensor color camera.
6. Have the possibility to have a larger displayed image
- For instance, as of now, we have a canvas element of 730×544 px², where the standard Basler camera for beamviewers have a sensor of 1296×966 px² which would largely fit on any modern monitor without scaling.
- We also have other Basler cameras with larger sensors on the beamlines.
7. Have the possibility to define the pixel size as a float, now only accepts integer.
- Useful for microscopy applications.
8. Have a way to record one full-frame image (only the last image? i.e. when the acquisition has been stopped? with transformations applied)
- Ideally also have access to the full bitdepth of the sensor (they are capable of 12bit).
9. Have the possibility to have a histogram displayed
- useful to tune the exposure time/gain, in order to optimize the dynamic range of the image and avoid saturation.
Does any of these have been suggested by others?
Is there a roadmap of planned development(s)?
I am available to help test.
Cheershttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/25Wago integration2020-03-12T11:30:49+01:00Stuart FisherWago integrationLonger term aim to integrate wago / bliss deviceLonger term aim to integrate wago / bliss devicehttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/24Apply ROI offsets to profiles and beammark2020-03-12T11:29:23+01:00Stuart FisherApply ROI offsets to profiles and beammarkOnce an ROI is applied the profiles start from 0 again, we should apply the ROI x,y offset so that the position is consistent regardless of whether an ROI is appliedOnce an ROI is applied the profiles start from 0 again, we should apply the ROI x,y offset so that the position is consistent regardless of whether an ROI is appliedhttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/23Issues with multiple cameras2020-03-12T11:28:40+01:00Stuart FisherIssues with multiple camerasThis seems hard to reproduce but Veijo reports issues when multiple cameras running.
Check that:
* events do not cross talk (they are keyed so should not!). Noted that sometimes start in one camera, starts in another
* slowdown with mul...This seems hard to reproduce but Veijo reports issues when multiple cameras running.
Check that:
* events do not cross talk (they are keyed so should not!). Noted that sometimes start in one camera, starts in another
* slowdown with multiple cameras, check gevent statushttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/20Document "background" workflow2020-03-12T11:24:08+01:00Stuart FisherDocument "background" workflowIts really not clear how the background feature works, document this properly with hints within the appIts really not clear how the background feature works, document this properly with hints within the apphttps://gitlab.esrf.fr/limagroup/Lima-bpm-web-server/-/issues/16Read only client2020-02-07T14:30:57+01:00Stuart FisherRead only client@beteva had a thought that maybe it would be useful to have a read only bpm client where you could see the viewer but not fiddle with settings or start / stop acquisitions.@beteva had a thought that maybe it would be useful to have a read only bpm client where you could see the viewer but not fiddle with settings or start / stop acquisitions.