bliss issueshttps://gitlab.esrf.fr/bliss/bliss/-/issues2023-09-04T13:42:35+02:00https://gitlab.esrf.fr/bliss/bliss/-/issues/3929aalborg gaz flow controller doc2023-09-04T13:42:35+02:00Cyril Guilloudaalborg gaz flow controller docaalborg gaz flow controller docaalborg gaz flow controller docCyril GuilloudCyril Guilloudhttps://gitlab.esrf.fr/bliss/bliss/-/issues/3778Add scriv/black/flake8 usage to CONTRIBUTING.md2023-05-15T13:47:30+02:00Wout De NolfAdd scriv/black/flake8 usage to CONTRIBUTING.mdhttps://gitlab.esrf.fr/bliss/bliss/-/issues/3411`broadcast_len` parameter to document2022-06-13T15:03:32+02:00Cyril Guilloud`broadcast_len` parameter to document`broadcast_len` parameter to document.
in `bliss/scanning/acquisition/motor.py`
`class VariableStepTriggerMaster(AcquisitionMaster)`
```python
def trigger(self):
self.trigger_slaves()
if self.broadcast_len > 1:
...`broadcast_len` parameter to document.
in `bliss/scanning/acquisition/motor.py`
`class VariableStepTriggerMaster(AcquisitionMaster)`
```python
def trigger(self):
self.trigger_slaves()
if self.broadcast_len > 1:
self.channels.update_from_iterable(
[
numpy.ones(self.broadcast_len, float) * axis.position
for axis in self._monitor_axes
]
)
else:
self.channels.update_from_iterable(
[axis.position for axis in self._monitor_axes]
)
self.wait_slaves()
```
used on id01 and id13:
```
[guilloud@pcsht]$ grep -nr broadcast_len *
id01/id01/scripts/ID01_sxdm.py:492: *slow_motors_positions, broadcast_len=x_nb_points
id01/id01/scripts/kmap.py:482: *slow_motors_positions, broadcast_len=x_nb_points
id13/id13/scripts/kmap.py:362: *slow_motors_positions, broadcast_len=x_nb_points
```https://gitlab.esrf.fr/bliss/bliss/-/issues/3347Axis doc about 'steps_position_precision' and 'precision'2023-01-26T10:14:41+01:00Cyril GuilloudAxis doc about 'steps_position_precision' and 'precision'`steps_position_precision`
`precision``steps_position_precision`
`precision`https://gitlab.esrf.fr/bliss/bliss/-/issues/3344Doc: 1.9 doc again missing, search bar again broken2022-05-02T16:31:03+02:00Valentin VallsDoc: 1.9 doc again missing, search bar again brokenRelated to #3331
Feedback from ID01Related to #3331
Feedback from ID01https://gitlab.esrf.fr/bliss/bliss/-/issues/3331Doc: Rework pages publishing using gitlab concepts2022-05-02T15:51:56+02:00Valentin VallsDoc: Rework pages publishing using gitlab conceptsThe actual solution used by BLISS to publish doc from multiple version is to
1. download the previous state of the web content (`wget`)
2. merge with it the result of the CI build (`cp` and stuff like that)
3. publish the new state in `...The actual solution used by BLISS to publish doc from multiple version is to
1. download the previous state of the web content (`wget`)
2. merge with it the result of the CI build (`cp` and stuff like that)
3. publish the new state in `public`
That's a dirty way because
- if wget fails, you lose the previous documentation #3330
- the content grow and grow up
gitlab allow to isolate each doc publicartion on it's own `public/FOO`.
There is no need to depend on `wget`.https://gitlab.esrf.fr/bliss/bliss/-/issues/3305function equivalent to Spec 'curs' (from cenpiccurs)2022-04-08T08:43:02+02:00Cyril Guilloudfunction equivalent to Spec 'curs' (from cenpiccurs)function equivalent to Spec 'curs' (from cenpiccurs)
~ to draw a cursor allowing user to go to a particular point
* [ ] doc
* [ ] tests
poke @valentin.valls
```
/segfs/bliss/source/spec/macros/graphical.mac
/segfs/bliss/source/spec/...function equivalent to Spec 'curs' (from cenpiccurs)
~ to draw a cursor allowing user to go to a particular point
* [ ] doc
* [ ] tests
poke @valentin.valls
```
/segfs/bliss/source/spec/macros/graphical.mac
/segfs/bliss/source/spec/macros/cenpiccurs.mac
```
```python
if (_key == "q"){
exit
}
else if (_key == "+"){
__i++
}
else if (_key == "-") {
__i--
}
else if (_key == "g"){
#__mystr = sprintf("umv " motor_mne(_m[0]) " " SCAN_D[__i][pl_x])
__mystr = "umv " motor_mne(_m[0]) " " SCAN_D[__i][pl_x]
print __mystr
eval(__mystr)
exit
}
else{
print "what ??"
}
```Gilles BerruyerGilles Berruyerhttps://gitlab.esrf.fr/bliss/bliss/-/issues/3009opiomoutput2021-10-08T14:17:44+02:00Cyril Guilloudopiomoutputopiomoutput
* doc
* `__info__()`opiomoutput
* doc
* `__info__()`Cyril GuilloudCyril Guilloudhttps://gitlab.esrf.fr/bliss/bliss/-/issues/2794doc disabled_cache2021-06-04T11:48:53+02:00Cyril Guillouddoc disabled_cachedoc disabled_cachedoc disabled_cacheCyril GuilloudCyril Guilloudhttps://gitlab.esrf.fr/bliss/bliss/-/issues/2619doc bliss_ds2021-03-08T18:02:08+01:00Cyril Guillouddoc bliss_dsdoc bliss_dsdoc bliss_dsCyril GuilloudCyril Guilloudhttps://gitlab.esrf.fr/bliss/bliss/-/issues/2343doc: API for bliss version is not online2021-03-12T09:59:57+01:00Valentin Vallsdoc: API for bliss version is not onlineLooks like the API for version like 1.5.0 are not generated
Master is there but, not versions
- https://bliss.gitlab-pages.esrf.fr/bliss/master/api/index.html
- https://bliss.gitlab-pages.esrf.fr/bliss/1.5.0/api/index.html
- https://bli...Looks like the API for version like 1.5.0 are not generated
Master is there but, not versions
- https://bliss.gitlab-pages.esrf.fr/bliss/master/api/index.html
- https://bliss.gitlab-pages.esrf.fr/bliss/1.5.0/api/index.html
- https://bliss.gitlab-pages.esrf.fr/bliss/1.6.0/api/index.htmlhttps://gitlab.esrf.fr/bliss/bliss/-/issues/1850update doc section about get_data2020-07-07T11:20:36+02:00Linus Pithanupdate doc section about get_datahttps://bliss.gitlab-pages.esrf.fr/bliss/master/scan_engine_scan.html#scan-data
seems to be outdated. It does not mention that also counters and motors can be used as keys in `scan.get_data`https://bliss.gitlab-pages.esrf.fr/bliss/master/scan_engine_scan.html#scan-data
seems to be outdated. It does not mention that also counters and motors can be used as keys in `scan.get_data`https://gitlab.esrf.fr/bliss/bliss/-/issues/1698BLISS / lima doc2022-01-25T16:51:05+01:00Cyril GuilloudBLISS / lima docmissing doc for: BLISS lima
* `limatake`
* `limastat`
How to :
* take an image
* save images
* configure lima in scans
* add lima metadata
* take background
*
*
*missing doc for: BLISS lima
* `limatake`
* `limastat`
How to :
* take an image
* save images
* configure lima in scans
* add lima metadata
* take background
*
*
*https://gitlab.esrf.fr/bliss/bliss/-/issues/930discussion about scan_info2021-05-01T00:11:38+02:00Linus Pithandiscussion about scan_infolooking at `scan_info` there are some questions/remarks based on a discussion with @denolf. Here are two `scan_info`s (only relevant part) for two different scans that we will base the discussion on
```
BLISS [53]: s=dmesh(roby,0,1,10,r...looking at `scan_info` there are some questions/remarks based on a discussion with @denolf. Here are two `scan_info`s (only relevant part) for two different scans that we will base the discussion on
```
BLISS [53]: s=dmesh(roby,0,1,10,robz,0,1,10,.1,diode)
BLISS [54]: pprint( s.scan_info)
{
'acquisition_chain': {'axis': {
...
'master': {
'scalars': ['axis:roby',
'axis:robz'],
...
}
},
'data_dim': 2,
'npoints': 100,
'npoints1': 10,
'npoints2': 10,
'start': [1.0, 2.0],
'stop': [2.0, 3.0],
'title': 'dmesh roby 0 1 10 robz 0 1 10 0.1',
'type': 'dmesh',
...
}
BLISS [55]: s=a2scan(roby,0,1,robz,0,1,10,.1,diode)
BLISS [56]: pprint( s.scan_info)
{
'acquisition_chain': {'axis': {
...
'master': {
'scalars': ['axis:roby',
'axis:robz'],
...
}
},
'npoints': 10,
'start': [0, 0],
'stop': [1, 1],
'title': 'a2scan roby 0 1 robz 0 1 10 0.1',
'type': 'a2scan',
...
}
```
here are some questions:
- why is the 'data_dim' entry not alwas there?
- what defines to which axis the entries in 'start' and 'stop' correspond? is it always the same order as 'scan_info['acquisition_chain']['axis']['master']['scalars']'?
- while 'start' and 'stop' are lists, why `npoints1`, `npoints2`... are not also in a single list (:warning: it is clear that npoints# is linked to the dimension of the scan and not to number of axis as it is the case for `start` and `stop`)
- could `'display_names'` be an entry of `scan_info` (see #779 and #922)?https://gitlab.esrf.fr/bliss/bliss/-/issues/927doc on scan number handling2019-08-08T13:04:23+02:00Linus Pithandoc on scan number handling@denolf pointed out that currently there is no __doc__ about the handling of __scan_numbers__ e.g.
- when are the reset?
- can you reset them manually?
- where is the persistent information about the scan number kept? i.e. how does blis...@denolf pointed out that currently there is no __doc__ about the handling of __scan_numbers__ e.g.
- when are the reset?
- can you reset them manually?
- where is the persistent information about the scan number kept? i.e. how does bliss now with which scan number to continue when changing `SCAN_SAVING` entries to an already existing filehttps://gitlab.esrf.fr/bliss/bliss/-/issues/642Motion framework, write user documentation about Group objects2019-07-30T10:26:42+02:00Matias GuijarroMotion framework, write user documentation about Group objectsExplain what are `Group` objects (from `bliss.common.motor_group`),
and write user documentation about those objects features.Explain what are `Group` objects (from `bliss.common.motor_group`),
and write user documentation about those objects features.https://gitlab.esrf.fr/bliss/bliss/-/issues/542pi_e8712021-05-02T01:30:54+02:00Matias Guijarropi_e871* [x] test and adapt (if needed) PI E871 motor controller to Python 3
* [ ] write configuration documentation
(model present on ID16b ?)* [x] test and adapt (if needed) PI E871 motor controller to Python 3
* [ ] write configuration documentation
(model present on ID16b ?)Cyril GuilloudCyril Guilloudhttps://gitlab.esrf.fr/bliss/bliss/-/issues/438documentation: update info about SCAN_SAVING2021-04-30T10:59:17+02:00Matias Guijarrodocumentation: update info about SCAN_SAVINGSCAN_SAVING has new features: image_template etc.SCAN_SAVING has new features: image_template etc.https://gitlab.esrf.fr/bliss/bliss/-/issues/320Documentation for user scripts2021-05-02T02:15:23+02:00Matias GuijarroDocumentation for user scriptsTODO: **how to start writing scripts for BLISS**
* [x] where to put code (`sessions/scripts` or somewhere else, it depends)
* [ ] explain `from bliss.setup_globals import ...`
* [ ] explain `cleanup` context managers
* [ ] show some exa...TODO: **how to start writing scripts for BLISS**
* [x] where to put code (`sessions/scripts` or somewhere else, it depends)
* [ ] explain `from bliss.setup_globals import ...`
* [ ] explain `cleanup` context managers
* [ ] show some example code