Skip to content

Commit

Permalink
Deploying to gh-pages from @ e8af6cc 🚀
Browse files Browse the repository at this point in the history
  • Loading branch information
@tbirdso
tbirdso committed Jul 31, 2024
1 parent 526cad5 commit ce81f05
Showing 1 changed file with 117 additions and 0 deletions.
117 changes: 117 additions & 0 deletions aggregate_metadata.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -939,6 +939,123 @@
"source_folder": "applications",
"build_and_run": "./dev_container build_and_run network_radar_pipeline --language cpp"
},
{
"metadata": {
"name": "Holoviz vsync",
"authors": [
{
"name": "Holoscan Team",
"affiliation": "NVIDIA"
}
],
"language": "C++",
"version": "1.0.0",
"changelog": {
"1.0": "Initial Release"
},
"holoscan_sdk": {
"minimum_required_version": "2.3",
"tested_versions": [
"2.3"
]
},
"platforms": [
"amd64",
"arm64"
],
"tags": [
"Holoviz vsync"
],
"ranking": 1,
"dependencies": {},
"run": {
"command": "<holohub_app_bin>/holoviz/holoviz_vsync",
"workdir": "holohub_bin"
}
},
"readme": "# Holoviz vsync\n\n![](holoviz_vsync.png)<br>\nThis application demonstrates the capability of the Holoviz operator to wait for the vertical blank of the display before updating the current image. It prints the displayed frames per second to the console, if sync to vertical blank is enabled the frames per second are capped to the display refresh rate.\n\nTo enable syncing to vertical blank set the `vsync` parameter of the Holoviz operator to `true`:\n\n```cpp\n auto holoviz = make_operator<ops::HolovizOp>(\n \"holoviz\",\n // enable synchronization to vertical blank\n Arg(\"vsync\", true));\n```\n\nBy default, the Holoviz operator is not syncing to the vertical blank of the display.\n\n## Run Instructions\n\nTo build and start the application:\n\n```bash\n./dev_container build_and_run holoviz_vsync\n```\n",
"application_name": "holoviz_vsync",
"source_folder": "applications",
"build_and_run": "./dev_container build_and_run holoviz_vsync --language cpp"
},
{
"metadata": {
"name": "{{ cookiecutter.project_name }}",
"authors": [
{
"name": "{{ cookiecutter.full_name }}",
"affiliation": "NVIDIA"
}
],
"language": "C++",
"version": "1.0.0",
"changelog": {
"1.0": "Initial Release"
},
"holoscan_sdk": {
"minimum_required_version": "{{ cookiecutter.holoscan_version }}",
"tested_versions": [
"{{ cookiecutter.holoscan_version }}"
]
},
"platforms": [
"amd64",
"arm64"
],
"tags": [
"{{ cookiecutter.project_name }}"
],
"ranking": 1,
"dependencies": {},
"run": {
"command": "<holohub_app_bin>/holoviz/{{ cookiecutter.project_slug }}",
"workdir": "holohub_bin"
}
},
"readme": "# {{ cookiecutter.project_name }}\n\n![]({{ cookiecutter.project_slug }}.png)<br>\n\n{%- if cookiecutter.example == \"sRGB\" %}\nThis application demonstrates the handling of the sRGB color space supported by the Holoviz operator.\n\nThe Holoviz operator can convert sRGB input images to linear color space before rendering and also can convert from linear color space to sRGB before writing to the frame buffer.\n\nsRGB color space can be enabled for input images and for the frame buffer independently. By default, the sRGB color space is disabled for both.\n\nBy default, the Holoviz operator is auto detecting the input image format. Auto detection always assumes linear color space for input images. To change this to sRGB color space explicitly set the `image_format_` member of the input spec for that input image to a format ending with `SRGB`:\n\n```cpp\n // By default the image format is auto detected. Auto detection assumes linear color space,\n // but we provide an sRGB encoded image. Create an input spec and change the image format to\n // sRGB.\n ops::HolovizOp::InputSpec input_spec(\"image\", ops::HolovizOp::InputType::COLOR);\n input_spec.image_format_ = ops::HolovizOp::ImageFormat::R8G8B8_SRGB;\n\n auto holoviz = make_operator<ops::HolovizOp>(\n \"holoviz\",\n Arg(\"tensors\", std::vector<ops::HolovizOp::InputSpec>{input_spec}));\n```\n\nBy default, the frame buffer is using linear color space. To use the sRGB color space, set the `framebuffer_srbg` argument of the Holoviz operator to `true`:\n\n```cpp\n auto holoviz = make_operator<ops::HolovizOp>(\n \"holoviz\",\n // enable the sRGB frame buffer\n Arg(\"framebuffer_srbg\", true));\n```\n\n{%- endif %}\n{%- if cookiecutter.example == \"vsync\" %}\nThis application demonstrates the capability of the Holoviz operator to wait for the vertical blank of the display before updating the current image. It prints the displayed frames per second to the console, if sync to vertical blank is enabled the frames per second are capped to the display refresh rate.\n\nTo enable syncing to vertical blank set the `vsync` parameter of the Holoviz operator to `true`:\n\n```cpp\n auto holoviz = make_operator<ops::HolovizOp>(\n \"holoviz\",\n // enable synchronization to vertical blank\n Arg(\"vsync\", true));\n```\n\nBy default, the Holoviz operator is not syncing to the vertical blank of the display.\n{%- endif %}\n\n## Run Instructions\n\nTo build and start the application:\n\n```bash\n./dev_container build_and_run {{ cookiecutter.project_slug }}\n```\n",
"application_name": "{{cookiecutter.project_slug}}",
"source_folder": "applications",
"build_and_run": "./dev_container build_and_run {{cookiecutter.project_slug}} --language cpp"
},
{
"metadata": {
"name": "Holoviz sRGB",
"authors": [
{
"name": "Holoscan Team",
"affiliation": "NVIDIA"
}
],
"language": "C++",
"version": "1.0.0",
"changelog": {
"1.0": "Initial Release"
},
"holoscan_sdk": {
"minimum_required_version": "2.3",
"tested_versions": [
"2.3"
]
},
"platforms": [
"amd64",
"arm64"
],
"tags": [
"Holoviz sRGB"
],
"ranking": 1,
"dependencies": {},
"run": {
"command": "<holohub_app_bin>/holoviz/holoviz_srgb",
"workdir": "holohub_bin"
}
},
"readme": "# Holoviz sRGB\n\n![](holoviz_srgb.png)<br>\nThis application demonstrates the handling of the sRGB color space supported by the Holoviz operator.\n\nThe Holoviz operator can convert sRGB input images to linear color space before rendering and also can convert from linear color space to sRGB before writing to the frame buffer.\n\nsRGB color space can be enabled for input images and for the frame buffer independently. By default, the sRGB color space is disabled for both.\n\nBy default, the Holoviz operator is auto detecting the input image format. Auto detection always assumes linear color space for input images. To change this to sRGB color space explicitly set the `image_format_` member of the input spec for that input image to a format ending with `SRGB`:\n\n```cpp\n // By default the image format is auto detected. Auto detection assumes linear color space,\n // but we provide an sRGB encoded image. Create an input spec and change the image format to\n // sRGB.\n ops::HolovizOp::InputSpec input_spec(\"image\", ops::HolovizOp::InputType::COLOR);\n input_spec.image_format_ = ops::HolovizOp::ImageFormat::R8G8B8_SRGB;\n\n auto holoviz = make_operator<ops::HolovizOp>(\n \"holoviz\",\n Arg(\"tensors\", std::vector<ops::HolovizOp::InputSpec>{input_spec}));\n```\n\nBy default, the frame buffer is using linear color space. To use the sRGB color space, set the `framebuffer_srbg` argument of the Holoviz operator to `true`:\n\n```cpp\n auto holoviz = make_operator<ops::HolovizOp>(\n \"holoviz\",\n // enable the sRGB frame buffer\n Arg(\"framebuffer_srbg\", true));\n```\n\n## Run Instructions\n\nTo build and start the application:\n\n```bash\n./dev_container build_and_run holoviz_srgb\n```\n",
"application_name": "holoviz_srgb",
"source_folder": "applications",
"build_and_run": "./dev_container build_and_run holoviz_srgb --language cpp"
},
{
"metadata": {
"name": "matlab_image_processing",
Expand Down

0 comments on commit ce81f05

Please sign in to comment.