P. HanletFermi National Accelerator Laboratory, M. GonzalezFermi National Accelerator Laboratory, J. DiamondFermi National Accelerator Laboratory, K. S. MartinFermi National Accelerator Laboratory
{"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}
引用次数: 0
Abstract
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.
京公网安备 11010802042870号
京ICP备2023020795号-1
分享
求助内容：
应助结果提醒方式：
扫码关注我们
