diff --git a/broker/gen/model/Dataset_settings.h b/broker/gen/model/Dataset_settings.h
index c9e5d574..8a06b8e0 100644
--- a/broker/gen/model/Dataset_settings.h
+++ b/broker/gen/model/Dataset_settings.h
@@ -168,7 +168,7 @@ public:
bool gridScanIsSet() const;
void unsetGrid_scan();
///
- /// Header appendix, added as user_data/user to start ZeroMQ message (can be any valid JSON) In general, it is not saved in HDF5 file. However, if values are placed in \"hdf5\" object, `jfjoch_writer` will write them in /entry/data of the HDF5 file. This applies solely to string and number (double floating-point). No arrays/sub-objects is allowed. For example {\"hdf5\": {\"val1\":1, \"val2\":\"xyz\"}}, will write /entry/user/val1 and /entry/user/val2.
+ /// Header appendix, added as user_data/user to start ZeroMQ message (can be any valid JSON) In general, it is not saved in HDF5 file. However, if values are placed in \"hdf5\" object, `jfjoch_writer` will write them in /entry/user of the HDF5 file. This applies solely to string and number (double floating-point). No arrays/sub-objects is allowed. For example {\"hdf5\": {\"val1\":1, \"val2\":\"xyz\"}}, will write /entry/user/val1 and /entry/user/val2.
///
nlohmann::json getHeaderAppendix() const;
void setHeaderAppendix(nlohmann::json const& value);
diff --git a/broker/gen/model/Jfjoch_settings.h b/broker/gen/model/Jfjoch_settings.h
index e1e2ab26..8661427a 100644
--- a/broker/gen/model/Jfjoch_settings.h
+++ b/broker/gen/model/Jfjoch_settings.h
@@ -164,7 +164,7 @@ public:
bool receiverThreadsIsSet() const;
void unsetReceiver_threads();
///
- /// NUMA policy to bind CPUs
+ /// Ignored value
///
std::string getNumaPolicy() const;
void setNumaPolicy(std::string const& value);
diff --git a/broker/redoc-static.html b/broker/redoc-static.html
index 7475bf3e..e6a0dbfc 100644
--- a/broker/redoc-static.html
+++ b/broker/redoc-static.html
@@ -466,7 +466,7 @@ Transmission of attenuator (filter) [no units]
object (grid_scan)
Definition of a grid scan (mutually exclusive with rotation_axis)
header_appendix
any
Header appendix, added as user_data/user to start ZeroMQ message (can be any valid JSON)
In general, it is not saved in HDF5 file.
-
However, if values are placed in "hdf5" object, jfjoch_writer will write them in /entry/data of the HDF5 file.
+
However, if values are placed in "hdf5" object, jfjoch_writer will write them in /entry/user of the HDF5 file.
This applies solely to string and number (double floating-point). No arrays/sub-objects is allowed.
For example {"hdf5": {"val1":1, "val2":"xyz"}}, will write /entry/user/val1 and /entry/user/val2.
image_appendix
any
Image appendix, added as user_data to image ZeroMQ message (can be any valid JSON)
@@ -868,7 +868,7 @@ User mask is not automatically applied - i.e. pixels with user mask will have a
Test Jungfraujoch system
http://localhost:5232/preview/pedestal.tiff
Generate 1D plot from Jungfraujoch
query Parameters
binning
integer
Default: 1
Binning of frames for the plot (0 = default binning)
Fill value for elements that were missed during data collection
experimental_coord
boolean
Default: false
If measurement has goniometer axis defined, plot X-axis will represent rotation angle
If measurement has grid scan defined, plot X-axis and Y-axis will represent grid position, Z will be used as the final value
@@ -880,7 +880,7 @@ For still measurement the number is ignored
http://localhost:5232/preview/plot
Response samples
200
Content type
application/json
{
"title": "string",
"unit_x": "image_number",
"size_x": 0.1,
"size_y": 0.1,
"plot": [
{
"title": "",
"x": [
0.1
],
"y": [
0.1
],
"z": [
0.1
]
}
]
}
Generate 1D plot from Jungfraujoch and send in raw binary format.
Data are provided as (32-bit) float binary array.
This format doesn't transmit information about X-axis, only values, so it is of limited use for azimuthal integration.
-