{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":695268470,"defaultBranch":"main","name":"ad-aravis-epics-ioc","ownerLogin":"cnpem","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-09-22T18:18:51.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/131317218?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1726577381.0","currentOid":""},"activityList":{"items":[{"before":"839742d949b65247c8e478e4856cd1d6ce9ba851","after":null,"ref":"refs/heads/req","pushedAt":"2024-09-17T12:37:50.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"b1b8c5cd459216701fcb52d4664ac4006e9e8de8","after":"f20451cec3f616d415a7a962460873f74dcf5730","ref":"refs/heads/main","pushedAt":"2024-09-17T12:37:47.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"autosave: drop redundant ADBase requirements.\n\nADAravis autosave requirement file already includes ADGenICam\nrequirements, which in turn depends on `ADBase_settings.req`. Drop this\ndirect dependency on ADBase, avoiding all its PVs to become duplicated\nin the resulting .sav files.\n\nFixes: 7024f4ca3523 (autosave: configure autosave for driver and plugins.)","shortMessageHtmlLink":"autosave: drop redundant ADBase requirements."}},{"before":null,"after":"839742d949b65247c8e478e4856cd1d6ce9ba851","ref":"refs/heads/req","pushedAt":"2024-09-16T20:10:02.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"autosave: drop redundant ADBase requirements.\n\nADAravis autosave requirement file already includes ADGenICam\nrequirements, which in turn depends on `ADBase_settings.req`. Drop this\ndirect dependency on ADBase, avoiding all its PVs to become duplicated\nin the resulting .sav files.\n\nFixes: 7024f4ca3523 (autosave: configure autosave for driver and plugins.)","shortMessageHtmlLink":"autosave: drop redundant ADBase requirements."}},{"before":"78aa9284174e72d1eba747f0e06b44f1eaf31466","after":null,"ref":"refs/heads/cameras","pushedAt":"2024-09-16T19:07:24.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"adc4153fdbbfe7e25683859087017fe01579fda9","after":"b1b8c5cd459216701fcb52d4664ac4006e9e8de8","ref":"refs/heads/main","pushedAt":"2024-09-16T19:07:23.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: support Basler Ace models in SIRIUS beamlines.\n\nThese camera XML files have been gathered with arv-tool-0.8 of cameras\ncurrently deployed at SIRIUS beamlines. Using Area Detector R3-12-1's\nADGenICam makeDB.py script, they have been converted to the database\nfile with support for int64{in,out} record types.\n\nEntries from PixelFormat, ChunkSelector and ChunkPixelFormat exceeds the\n16 maximum values allowed for mbbi, and were kept as generated. The\nscript did not \"know what to do with Register\", but it should be fine\nfor us.","shortMessageHtmlLink":"database: support Basler Ace models in SIRIUS beamlines."}},{"before":"52e03020584da2822381e872024c3ea6508b7ac0","after":"78aa9284174e72d1eba747f0e06b44f1eaf31466","ref":"refs/heads/cameras","pushedAt":"2024-09-16T19:02:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: support Basler Ace models in SIRIUS beamlines.\n\nThese camera XML files have been gathered with arv-tool-0.8 of cameras\ncurrently deployed at SIRIUS beamlines. Using Area Detector R3-12-1's\nADGenICam makeDB.py script, they have been converted to the database\nfile with support for int64{in,out} record types.\n\nEntries from PixelFormat, ChunkSelector and ChunkPixelFormat exceeds the\n16 maximum values allowed for mbbi, and were kept as generated. The\nscript did not \"know what to do with Register\", but it should be fine\nfor us.","shortMessageHtmlLink":"database: support Basler Ace models in SIRIUS beamlines."}},{"before":"d46a0a4c1b5cf69db4c4860345514f61684b803d","after":"52e03020584da2822381e872024c3ea6508b7ac0","ref":"refs/heads/cameras","pushedAt":"2024-09-12T20:40:34.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: support Basler Ace models in SIRIUS beamlines.\n\nThese camera XML files have been gathered with arv-tool-0.8 of cameras\ncurrently deployed at SIRIUS beamlines. Using Area Detector R3-12-1's\nADGenICam makeDB.py script, they have been converted to the database\nfile with support for int64{in,out} record types.\n\nEntries from PixelFormat, ChunkSelector and ChunkPixelFormat exceeds the\n16 maximum values allowed for mbbi, and were kept as generated. The\nscript did not \"know what to do with Register\", but it should be fine\nfor us.","shortMessageHtmlLink":"database: support Basler Ace models in SIRIUS beamlines."}},{"before":"5414f5f9bccf989f949cd83175ccaed6673f3c30","after":null,"ref":"refs/heads/docker","pushedAt":"2024-09-11T20:17:18.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"9cfc7f8cf80a6d0ca61a4104336af6361d5bcf75","after":"adc4153fdbbfe7e25683859087017fe01579fda9","ref":"refs/heads/main","pushedAt":"2024-09-11T20:17:17.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"docker: upgrade to v0.10.0.\n\nThis fixes issues with autosave, which is a important dependency.\nMoreover, it improves the experience of running containers without\nsubuid and subgid, which is the default setting for SIRIUS beamlines.","shortMessageHtmlLink":"docker: upgrade to v0.10.0."}},{"before":null,"after":"5414f5f9bccf989f949cd83175ccaed6673f3c30","ref":"refs/heads/docker","pushedAt":"2024-09-06T17:50:52.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"docker: upgrade to v0.10.0.\n\nThis fixes issues with autosave, which is a important dependency.\nMoreover, it improves the experience of running containers without\nsubuid and subgid, which is the default setting for SIRIUS beamlines.","shortMessageHtmlLink":"docker: upgrade to v0.10.0."}},{"before":null,"after":"d46a0a4c1b5cf69db4c4860345514f61684b803d","ref":"refs/heads/cameras","pushedAt":"2024-09-05T20:43:45.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: support versions -18, -20 of Basler acA1300-75gm.\n\nThese camera XML files have been gathered with arv-tool-0.8 (0.8.26).\nUsing Area Detector R3-12-1's ADGenICam makeDB.py script, they have been\nconverted to the database file with support for int64{in,out} record\ntypes.\n\nEntries from PixelFormat, ChunkSelector and ChunkPixelFormat exceeds the\n16 maximum values allowed for mbbi, and were kept as generated. The\nscript did not \"know what to do with Register\", but it should be fine\nfor us.","shortMessageHtmlLink":"database: support versions -18, -20 of Basler acA1300-75gm."}},{"before":"0093e868dbdb90ac67df41b408826f58ffa5889a","after":null,"ref":"refs/heads/snapshot","pushedAt":"2024-05-07T19:12:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"38aabacabb841b0f5c3828a2abafe789e89ca1ac","after":"9cfc7f8cf80a6d0ca61a4104336af6361d5bcf75","ref":"refs/heads/main","pushedAt":"2024-05-07T19:00:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: reindex last field in snapshot and streaming.\n\nAll fields should follow a sequential order. Reindex the last one from\nboth Snapshot and Stream PVs to follow this. Also drop the extra delay\nmatching no PV.\n\nFix: 227446b (database: add high resolution snapshot and binned stream records.)","shortMessageHtmlLink":"database: reindex last field in snapshot and streaming."}},{"before":null,"after":"0093e868dbdb90ac67df41b408826f58ffa5889a","ref":"refs/heads/snapshot","pushedAt":"2024-05-07T17:00:19.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: delay on starting and stoping acquisition.\n\nThis seems to prevent not well understood issues with changing camera\nparameters and acquiring data from the camera when changing from\nsnapshot to stream or vice-versa. It should be further investigated why\nthis happens if that delaying is really needed.","shortMessageHtmlLink":"database: delay on starting and stoping acquisition."}},{"before":"9e044f72f7fa011ab8748b1b66621c25bb1f9b4c","after":null,"ref":"refs/heads/limits","pushedAt":"2024-04-24T19:20:03.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"227446b0bb28f29839dd95f420e50c52ce1a95dd","after":"38aabacabb841b0f5c3828a2abafe789e89ca1ac","ref":"refs/heads/main","pushedAt":"2024-04-24T19:20:03.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: forward rate limit to FrameRate.DRVH.\n\nBoth AcquirePeriod and FrameRate can be used to define frame rate. Keep\ntheir limits consistent by forwarding the inverse of period limit to the\nFrameRate record.\n\nA better implementation of this feature would to have a FrameRateLimit\nrecord which forwards for both AcquirePeriod's and FrameRate's DRVL and\nDRLH fields. Having the limit specified in terms of frame rate would\nhowever would require changing the configuration parameter defined in\nthe template st.cmd.\n\nTo keep backward compatibility, the frame rate is computed based on the\nvalue of the AcquirePeriod.DRVL instead. Changing it at runtime requires\nreprocessing FrameRateLimitFwd to forward to FrameRate.DRVH.","shortMessageHtmlLink":"database: forward rate limit to FrameRate.DRVH."}},{"before":"2d3aa06b58121922bfbb24009bf811b3777c601b","after":"9e044f72f7fa011ab8748b1b66621c25bb1f9b4c","ref":"refs/heads/limits","pushedAt":"2024-04-24T17:28:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: forward rate limit to FrameRate.DRVH.\n\nBoth AcquirePeriod and FrameRate can be used to define frame rate. Keep\ntheir limits consistent by forwarding the inverse of period limit to the\nFrameRate record.\n\nA better implementation of this feature would to have a FrameRateLimit\nrecord which forwards for both AcquirePeriod's and FrameRate's DRVL and\nDRLH fields. Having the limit specified in terms of frame rate would\nhowever would require changing the configuration parameter defined in\nthe template st.cmd.\n\nTo keep backward compatibility, the frame rate is computed based on the\nvalue of the AcquirePeriod.DRVL instead. Changing it at runtime requires\nreprocessing FrameRateLimitFwd to forward to FrameRate.DRVH.","shortMessageHtmlLink":"database: forward rate limit to FrameRate.DRVH."}},{"before":"a33d1471349d007a33a77ebb485590f4bb821c35","after":"2d3aa06b58121922bfbb24009bf811b3777c601b","ref":"refs/heads/limits","pushedAt":"2024-04-24T17:20:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: forward rate limit to FrameRate.DRVH.\n\nBoth AcquirePeriod and FrameRate can be used to define frame rate. Keep\ntheir limits consistent by forwarding the inverse of period limit to the\nFrameRate record.\n\nAn better implementation of this feature is to have a FrameRateLimit\nrecord which forwards for both AcquirePeriod's and FrameRate's DRVL and\nDRLH fields. Having the limit specified in terms of frame rate would\nhowever would require changing the configuration parameter defined in\nthe template st.cmd.\n\nTo keep backward compatibility, the frame rate is computed based on the\nvalue of the AcquirePeriod.DRVL instead. Changing it at runtime requires\nreprocessing FrameRateLimitFwd to forward to FrameRate.DRVH.","shortMessageHtmlLink":"database: forward rate limit to FrameRate.DRVH."}},{"before":"4a1486858041a014955853108c0e1fdf23f67e01","after":"a33d1471349d007a33a77ebb485590f4bb821c35","ref":"refs/heads/limits","pushedAt":"2024-04-24T13:09:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: forward rate limit to FrameRate.DRVH.\n\nBoth AcquirePeriod and FrameRate can be used to define frame rate. Keep\ntheir limits consistent by forwarding the inverse of period limit to the\nFrameRate record.\n\nTo keep backward compatibility, the frame rate is computed based on the\nvalue of the AcquirePeriod.DRVL. Changing that at runtime requires\nreprocessing FrameRateLimitFwd to forward to FrameRate.DRVH.\n\nAn alternative implementation of this feature is to have a\nFrameRateLimit record which forwards for both AcquirePeriod and\nFrameRate DRVL and DRLH fields. However, this cannot be easily\nimplemented without changing the external API of defining\nACQUIRE_PERIOD_DRVL alone.","shortMessageHtmlLink":"database: forward rate limit to FrameRate.DRVH."}},{"before":"227446b0bb28f29839dd95f420e50c52ce1a95dd","after":null,"ref":"refs/heads/snapshot","pushedAt":"2024-04-23T20:56:33.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"a94d5b1add670323ad7ef25ce93d3e470f28999b","after":"227446b0bb28f29839dd95f420e50c52ce1a95dd","ref":"refs/heads/main","pushedAt":"2024-04-23T20:56:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: add high resolution snapshot and binned stream records.\n\nMost cameras have high-throughput when operating with its full\nresolution. To make it possible to run at higher frame rates when\nstreaming, add new records to enable and disable binning feature and\nchange the resolution correspondingly.\n\nUsing channel access links to `Acquire` is required here to have the\ndesired effect. Otherwise, sometimes the record won't be reprocessed at\nthe right time (blocking with RPRO=1). This issue has not been further\ninvestigated, but has not shown to occur with channel access links. To\navoid delays and have explicit support for waiting for record\nprocessing, sseq from calc module is used. It should be further\ninvestigated if checking for read-back values is more appropriate to\nensure the setting is satisfied.\n\nEven though the camera firmware knows which value is the updated maximum\nwhen applying binning, it does not deliver the image when such parameter\nis not explicitly reset. Thus, the operation mode switch must enforce\nthis. In a similar vein, GC_{Height,Width}Max_RBV do not update in time\nwhen decreasing binning. Thus, use `GC_Sensor{Height,Width}_RBV` instead\nto avoid empirical delays. Curiously, this does not apply to\n`$(P)$(R)Stream`. These can possibly be fixed by waiting for read-backs.\n\nThis has been tested with a Alvium G1-500c. Some features, such as\nbinning mode, may have different names for other devices, which may lead\nto unexpected behaviours. It should be refactored to use uniform records\nif another camera is to be supported for this operation mode.\n\nA template (cmd) script is provided to make it easier to load such\nrecords in a clean way in the main start-up script.","shortMessageHtmlLink":"database: add high resolution snapshot and binned stream records."}},{"before":"7718fe5454d689c4e111f33c23bffe4dd8b73ee6","after":"227446b0bb28f29839dd95f420e50c52ce1a95dd","ref":"refs/heads/snapshot","pushedAt":"2024-04-23T20:55:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: add high resolution snapshot and binned stream records.\n\nMost cameras have high-throughput when operating with its full\nresolution. To make it possible to run at higher frame rates when\nstreaming, add new records to enable and disable binning feature and\nchange the resolution correspondingly.\n\nUsing channel access links to `Acquire` is required here to have the\ndesired effect. Otherwise, sometimes the record won't be reprocessed at\nthe right time (blocking with RPRO=1). This issue has not been further\ninvestigated, but has not shown to occur with channel access links. To\navoid delays and have explicit support for waiting for record\nprocessing, sseq from calc module is used. It should be further\ninvestigated if checking for read-back values is more appropriate to\nensure the setting is satisfied.\n\nEven though the camera firmware knows which value is the updated maximum\nwhen applying binning, it does not deliver the image when such parameter\nis not explicitly reset. Thus, the operation mode switch must enforce\nthis. In a similar vein, GC_{Height,Width}Max_RBV do not update in time\nwhen decreasing binning. Thus, use `GC_Sensor{Height,Width}_RBV` instead\nto avoid empirical delays. Curiously, this does not apply to\n`$(P)$(R)Stream`. These can possibly be fixed by waiting for read-backs.\n\nThis has been tested with a Alvium G1-500c. Some features, such as\nbinning mode, may have different names for other devices, which may lead\nto unexpected behaviours. It should be refactored to use uniform records\nif another camera is to be supported for this operation mode.\n\nA template (cmd) script is provided to make it easier to load such\nrecords in a clean way in the main start-up script.","shortMessageHtmlLink":"database: add high resolution snapshot and binned stream records."}},{"before":"32c83df87777fb31609516afff6b83be2bcc7cfe","after":"7718fe5454d689c4e111f33c23bffe4dd8b73ee6","ref":"refs/heads/snapshot","pushedAt":"2024-04-23T14:25:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: add high resolution snapshot and binned stream records.\n\nMost cameras have high-throughput when operating with its full\nresolution. To make it possible to run at higher frame rates when\nstreaming, add new records to enable and disable binning feature and\nchange the resolution correspondingly.\n\nUsing channel access links to `Acquire` is required here to have the\ndesired effect. Otherwise, sometimes the record won't be reprocessed at\nthe right time (blocking with RPRO=1). This issue has not been further\ninvestigated, but has not shown to occur with channel access links. To\navoid delays and have explicit support for waiting for record\nprocessing, sseq from calc module is used. It should be further\ninvestigated if checking for read-back values is more appropriate to\nensure the setting is satisfied.\n\nEven though the camera firmware knows which value is the updated maximum\nwhen applying binning, it does not deliver the image when such parameter\nis not explicitly reset. Thus, the operation mode switch must enforce\nthis. In a similar vein, GC_{Height,Width}Max_RBV do not update in time\nwhen decreasing binning. Thus, use `GC_Sensor{Height,Width}_RBV` instead\nto avoid empirical delays. Curiously, this does not apply to\n`$(P)$(R)Stream`. These can possibly be fixed by waiting for read-backs.\n\nThis has been tested with a Alvium G1-500c. Some features, such as\nbinning mode, may have different names for other devices, which may lead\nto unexpected behaviours. It should be refactored to use uniform records\nif another camera is to be supported for this operation mode.\n\nA template (cmd) script is provided to make it easier to load such\nrecords in a clean way in the main start-up script.","shortMessageHtmlLink":"database: add high resolution snapshot and binned stream records."}},{"before":"3d17eb56a5567c564e0197869e40304298551d19","after":null,"ref":"refs/heads/queue-size","pushedAt":"2024-04-17T13:40:55.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"}},{"before":"cfa9d46392fa4835cb946caa40266e0a70c7d5e4","after":"a94d5b1add670323ad7ef25ce93d3e470f28999b","ref":"refs/heads/main","pushedAt":"2024-04-17T13:40:54.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"plugins: define plugin queue sizes by default.\n\nMost camera IOCs will not require a custom queue size for plugins.\nDefine the previously recommended values as default, that is QSIZE=20\nfor all plugins but NDPluginHDF5, which takes a 50-element queue. This\nmakes the template script shorter and easier to maintain.\n\nThis change is backward compatible with previous versions, since the\nvariables are still used in the `plugins.cmd` template.","shortMessageHtmlLink":"plugins: define plugin queue sizes by default."}},{"before":"b7f7d32ecdd9c94dfb4790e835bc7f4b91ccb6e0","after":"3d17eb56a5567c564e0197869e40304298551d19","ref":"refs/heads/queue-size","pushedAt":"2024-04-17T12:00:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"plugins: define plugin queue sizes by default.\n\nMost camera IOCs will not require a custom queue size for plugins.\nDefine the previously recommended values as default, that is QSIZE=20\nfor all plugins but NDPluginHDF5, which takes a 50-element queue. This\nmakes the template script shorter and easier to maintain.\n\nThis change is backward compatible with previous versions, since the\nvariables are still used in the `plugins.cmd` template.","shortMessageHtmlLink":"plugins: define plugin queue sizes by default."}},{"before":"8ca0642a215c9c329d92c78a450d4044b188a810","after":"4a1486858041a014955853108c0e1fdf23f67e01","ref":"refs/heads/limits","pushedAt":"2024-04-11T18:11:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: forward rate limit to FrameRate.DRVH.\n\nBoth AcquirePeriod and FrameRate can be used to define frame rate. Keep\ntheir limits consistent by forwarding the inverse of period limit to the\nFrameRate record.\n\nTo keep backward compatibility, the frame rate is computed based on the\nvalue of the AcquirePeriod.DRVL. Changing that at runtime requires\nreprocessing AcquirePeriodLimitFwd to forward to FrameRate.DRVH.","shortMessageHtmlLink":"database: forward rate limit to FrameRate.DRVH."}},{"before":"32a87115cfeba451eeb3081e7470ec9181e541b3","after":"8ca0642a215c9c329d92c78a450d4044b188a810","ref":"refs/heads/limits","pushedAt":"2024-04-08T20:44:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: ensure frame rate is enabled when limiting it.\n\nSome cameras default to automatic frame rate mode when power-cycled.\nThis makes the acquire period limitation ineffective, as the parameter\nis ignored by the camera firmware.\n\nEnforce manual frame rate setting at IOC start-up when limiting frame\nrate. Note that the overwritten record already contains `PINI=YES` to\nwrite this to hardware on `iocInit`.\n\nFixes: d5caf77 (\"database: add option to limit camera frame rate.\")","shortMessageHtmlLink":"database: ensure frame rate is enabled when limiting it."}},{"before":null,"after":"32a87115cfeba451eeb3081e7470ec9181e541b3","ref":"refs/heads/limits","pushedAt":"2024-04-08T20:25:36.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"database: ensure frame rate is enabled when limiting it.\n\nSome cameras default to automatic frame rate mode when power-cycled.\nThis makes the acquire period limitation ineffective, as the parameter\nis ignored by the camera firmware.\n\nEnforce this setting when starting up the IOC when the frame rate\nlimitation is desired. Note that overwritten record already contains\n`PINI=YES` to write this to hardware on `iocInit`.\n\nFixes: d5caf77 (\"database: add option to limit camera frame rate.\")","shortMessageHtmlLink":"database: ensure frame rate is enabled when limiting it."}},{"before":null,"after":"b7f7d32ecdd9c94dfb4790e835bc7f4b91ccb6e0","ref":"refs/heads/queue-size","pushedAt":"2024-04-08T19:03:43.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"henriquesimoes","name":"Henrique F. Simões","path":"/henriquesimoes","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33237318?s=80&v=4"},"commit":{"message":"plugins: define plugin queue sizes by default.\n\nMost camera IOCs will not require a custom queue size for plugins.\nDefine the previously recommended values as default, that is QSIZE=20\nfor all plugins but NDPluginHDF5, which takes a 50-element queue. This\nmakes the template script shorter and easier to maintain.\n\nThis change is backward compatible with previous versions, since the\nvariables are still used in the `plugins.cmd` template.","shortMessageHtmlLink":"plugins: define plugin queue sizes by default."}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0xN1QxMjozNzo1MC4wMDAwMDBazwAAAAS4guvy","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0xN1QxMjozNzo1MC4wMDAwMDBazwAAAAS4guvy","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNC0wOFQxOTowMzo0My4wMDAwMDBazwAAAAQrRLh2"}},"title":"Activity · cnpem/ad-aravis-epics-ioc"}