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 "can automated program repair refine fault localization"):
  Abstract: Software bugs are prevalent in modern software systems and notoriously hard to debug manually. Therefore, a large body of research efforts have been dedicated to automated software debugging, including both automated fault localization and program repair. However, the existing fault localization techniques are usually ineffective on real-world software systems while even the most advanced program repair techniques can only fix a small ratio of real-world bugs. Although fault localization and program repair are inherently connected, we observe that in the literature their only connection is that program repair techniques usually use off-the-shelf fault localization techniques (e.g., Ochiai) to determine the potential candidate statements/elements for patching. In this work, we explore their connection in the other direction, i.e., can program repair in turn help with fault localization? In this way,we not only open a new dimension for more powerful fault localization, but also extend the application scope of program repair to all possible bugs (not only the bugs that can be directly automatically fixed).We have designed ProFL, a simplistic approach using patch-execution results (from program repair) as the feedback information for fault localization. The experimental results on the widely used Defects4J benchmark show that the basic ProFL can already localize 161 of the 395 studied bugs within Top-1, while state-of-the-art spectrum and mutation based fault localization techniques at most localize 117 within Top-1. We also demonstrate ProFL's effectiveness under different settings. Lastly, we show that ProFL can further boost state-of-the-art fault localization via both unsupervised and supervised learning.

Includes members:
  Member "getafix learning to fix bugs automatically":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "adversarial examples for models of code")
  Member "an empirical study of fault localization families and their combinations":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "explaining deep neural networks using spectrum based fault localization")
  Member "automatic software repair a bibliography":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "a recurrent neural network based patch recommender for linux kernel bugs")
  Member "automatic repair of real bugs in java a large scale experiment on the defects4j dataset":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "e apr mapping the effectiveness of automated program repair")
  Member "nopol automatic repair of conditional statement bugs in java programs":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "e apr mapping the effectiveness of automated program repair")
  Member "test case purification for improving fault localization":
    also connected through other hyperedges:
      - Hyperedge HE-6 (induced by source paper "tbar revisiting template based automated program repair")
  Member "automated fixing of programs with contracts":
    also connected through other hyperedges:
      - Hyperedge HE-7 (induced by source paper "validation of automatically generated patches an appetizer")

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)