human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "continuous experimentation for automotive software on the example of a heavy commercial vehicle in daily operation"):
  Abstract: As the automotive industry focuses their efforts more and more towards the software end of the spectrum, techniques to deliver new software value at a fast pace are needed. Continuous Experimentation, a practice coming from the web-based systems world, is one of such techniques. It enables researchers and developers to use real-world data to verify their hypothesis and steer the software evolution based on performances and user preferences, reducing the reliance on simulations and guesswork. Several challenges prevent the verbatim adoption of this practice on automotive cyber-physical systems, e.g., safety concerns and computational resources limitations; nonetheless, the automotive field is starting to take interest in this technique. This work aims at demonstrating and evaluating a prototypical Continuous Experimentation cycle, performed on a distributed computational system housed in a commercial truck tractor that is used in daily operations by a logistic company. The system comprises computing units and sensors, and is only accessible remotely via a mobile connection, which is also the only communication channel that can be used for software deployment and data retrieval. The experimentation process resulted in the team being able to base software development choices on the real-world data collected during the experimental procedure. Finally, a set of previously identified design criteria to enable Continuous Experimentation on automotive systems was discussed in light of the presented work.

Includes members:
  Member "the automotive take on continuous experimentation a multiple case study":
    also connected through other hyperedges:
      (none)
  Member "design criteria to architect continuous experimentation for self driving vehicles":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "continuous experimentation and the cyber physical systems challenge an overview in literature and the industrial perspective")
  Member "microsoft coco common objects in context":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "mast a memory augmented self supervised tracker")

Question: Please tell me which class the source paper belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)