P. HanletFermi National Accelerator Laboratory, M. GonzalezFermi National Accelerator Laboratory, J. DiamondFermi National Accelerator Laboratory, K. S. MartinFermi National Accelerator Laboratory
{"title":"在费米实验室部署 Epics","authors":"P. HanletFermi National Accelerator Laboratory, M. GonzalezFermi National Accelerator Laboratory, J. DiamondFermi National Accelerator Laboratory, K. S. MartinFermi National Accelerator Laboratory","doi":"arxiv-2408.00174","DOIUrl":null,"url":null,"abstract":"Fermilab has traditionally not been an EPICS house; as such expertise in\nEPICS is limited and scattered. PIP-II will be using EPICS for its control\nsystem. When in operation, it will need to interface with the existing,\nmodernized (see ACORN) legacy control system. Treating EPICS controls at\nFermilab as a green field, we have developed and deployed a software pipeline\nwhich addresses these needs and presents to developers a tested and robust\nsoftware framework, including template IOCs from which new developers can\nquickly deploy new front ends, aka IOCs. In this presentation, motivation for\nthis work, implementation of a continuous integration/continuous deployment\npipeline, testing, template IOCs, and the deployment of user\nservices/applications will be discussed. This new infrastructure of IOCs and\nservices is being developed and used in the PIP-II cryomodule teststand; our\nexperiences and lessons learned will be also be discussed.","PeriodicalId":501318,"journal":{"name":"arXiv - PHYS - Accelerator Physics","volume":"235 1","pages":""},"PeriodicalIF":0.0000,"publicationDate":"2024-07-31","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Epics Deployment at Fermilab\",\"authors\":\"P. HanletFermi National Accelerator Laboratory, M. GonzalezFermi National Accelerator Laboratory, J. DiamondFermi National Accelerator Laboratory, K. S. MartinFermi National Accelerator Laboratory\",\"doi\":\"arxiv-2408.00174\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Fermilab has traditionally not been an EPICS house; as such expertise in\\nEPICS is limited and scattered. PIP-II will be using EPICS for its control\\nsystem. When in operation, it will need to interface with the existing,\\nmodernized (see ACORN) legacy control system. Treating EPICS controls at\\nFermilab as a green field, we have developed and deployed a software pipeline\\nwhich addresses these needs and presents to developers a tested and robust\\nsoftware framework, including template IOCs from which new developers can\\nquickly deploy new front ends, aka IOCs. In this presentation, motivation for\\nthis work, implementation of a continuous integration/continuous deployment\\npipeline, testing, template IOCs, and the deployment of user\\nservices/applications will be discussed. This new infrastructure of IOCs and\\nservices is being developed and used in the PIP-II cryomodule teststand; our\\nexperiences and lessons learned will be also be discussed.\",\"PeriodicalId\":501318,\"journal\":{\"name\":\"arXiv - PHYS - Accelerator Physics\",\"volume\":\"235 1\",\"pages\":\"\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2024-07-31\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"arXiv - PHYS - Accelerator Physics\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/arxiv-2408.00174\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"arXiv - PHYS - Accelerator Physics","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/arxiv-2408.00174","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
摘要
费米实验室历来不是 EPICS 研究机构;因此,EPICS 方面的专业知识有限而且分散。PIP-II 的控制系统将使用 EPICS。在运行时,它将需要与现有的、现代化的(见 ACORN)传统控制系统对接。我们将费米实验室的 EPICS 控制系统视为一块绿地,开发并部署了一个软件管道,以满足这些需求,并为开发人员提供了一个经过测试的强大软件框架,包括模板 IOC,新开发人员可以在此基础上快速部署新的前端(又称 IOC)。本讲座将讨论这项工作的动机、持续集成/持续部署管道的实施、测试、模板 IOC 以及用户服务/应用程序的部署。这种新的 IOC 和服务基础设施正在 PIP-II Cryomodule 测试台中开发和使用;我们的经验和教训也将得到讨论。
Fermilab has traditionally not been an EPICS house; as such expertise in
EPICS is limited and scattered. PIP-II will be using EPICS for its control
system. When in operation, it will need to interface with the existing,
modernized (see ACORN) legacy control system. Treating EPICS controls at
Fermilab as a green field, we have developed and deployed a software pipeline
which addresses these needs and presents to developers a tested and robust
software framework, including template IOCs from which new developers can
quickly deploy new front ends, aka IOCs. In this presentation, motivation for
this work, implementation of a continuous integration/continuous deployment
pipeline, testing, template IOCs, and the deployment of user
services/applications will be discussed. This new infrastructure of IOCs and
services is being developed and used in the PIP-II cryomodule teststand; our
experiences and lessons learned will be also be discussed.