human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "precise condition synthesis for program repair"
  Abstract: Due to the difficulty of repairing defect, many research efforts have been devoted into automatic defect repair. Given a buggy program that fails some test cases, a typical automatic repair technique tries to modify the program to make all tests pass. However, since the test suites in real world projects are usually insufficient, aiming at passing the test suites often leads to incorrect patches. #R##N#In this paper we aim to produce precise patches, that is, any patch we produce has a relatively high probability to be correct. More concretely, we focus on condition synthesis, which was shown to be able to repair more than half of the defects in existing approaches. Our key insight is threefold. First, it is important to know what variables in a local context should be used in an "if" condition, and we propose a sorting method based on the dependency relations between variables. Second, we observe that the API document can be used to guide the repair process, and propose document analysis technique to further filter the variables. Third, it is important to know what predicates should be performed on the set of variables, and we propose to mine a set of frequently used predicates in similar contexts from existing projects. #R##N#We develop a novel program repair system, ACS, that could generate precise conditions at faulty locations. Furthermore, given the generated conditions are very precise, we can perform a repair operation that is previously deemed to be too overfitting: directly returning the test oracle to repair the defect. Using our approach, we successfully repaired 18 defects on four projects of Defects4J, which is the largest number of fully automatically repaired defects reported on the dataset so far. More importantly, the precision of our approach in the evaluation is 78.3%, which is significantly higher than previous approaches, which are usually less than 40%.

Connected through hyperedge HE-1 (induced by source paper "encore ensemble learning using convolution neural machine translation for automatic program repair"):
  with members:
    - "a comprehensive study of automatic program repair on the quixbugs benchmark"
    - "sequencer sequence to sequence learning for end to end program repair"
    - "code2vec learning distributed representations of code"
    - "approaching neural grammatical error correction as a low resource machine translation task"
    - "reaching human level performance in automatic grammatical error correction an empirical study"
    - "a multilayer convolutional encoder decoder neural network for grammatical error correction"
    - "fixminer mining relevant fix patterns for automated program repair"
    - "tree2tree neural translation model for learning source code changes"

Connected through hyperedge HE-2 (induced by source paper "sequencer sequence to sequence learning for end to end program repair"):
  with members:
    - "on learning meaningful code changes via neural machine translation"
    - "maybe deep neural networks are the best choice for modeling source code"
    - "sorting and transforming program repair ingredients via deep learning code similarities"
    - "the codrep machine learning on source code competition"
    - "an empirical study of fault localization families and their combinations"
    - "automatic software repair a bibliography"
    - "code vectors understanding programs through embedded abstracted symbolic traces"
    - "learning to generate corrective patches using neural machine translation"

Connected through hyperedge HE-3 (induced by source paper "ifixr bug report driven program repair"):
  with members:
    - "d c a divide and conquer approach to ir based bug localization"
    - "tbar revisiting template based automated program repair"
    - "sorting and transforming program repair ingredients via deep learning code similarities"
    - "alleviating patch overfitting with automatic test generation a study of feasibility and effectiveness for the nopol repair system"
    - "getafix learning to fix bugs automatically"
    - "avatar fixing semantic bugs with fix patterns of static analysis violations"
    - "on reliability of patch correctness assessment"
    - "fixminer mining relevant fix patterns for automated program repair"

Connected through hyperedge HE-4 (induced by source paper "tbar revisiting template based automated program repair"):
  with members:
    - "bears an extensible java bug benchmark for automatic program repair studies"
    - "sorting and transforming program repair ingredients via deep learning code similarities"
    - "avatar fixing semantic bugs with fix patterns of static analysis violations"
    - "on reliability of patch correctness assessment"
    - "fixminer mining relevant fix patterns for automated program repair"
    - "automatic software repair a bibliography"
    - "ultra large repair search space with automatically mined templates the cardumen mode of astor"
    - "you cannot fix what you cannot find an investigation of fault localization bias in benchmarking automated program repair systems"

Connected through hyperedge HE-5 (induced by source paper "ir2vec a flow analysis based scalable infrastructure for program encodings"):
  with members:
    - "code2vec learning distributed representations of code"
    - "neural code comprehension a learnable representation of code semantics"
    - "a general path based representation for predicting program properties"
    - "a survey of machine learning for big code and naturalness"
    - "abstract syntax networks for code generation and semantic parsing"
    - "learning to represent programs with graphs"
    - "dynamic neural program embedding for program repair"
    - "source forager a search engine for similar source code"

Connected through hyperedge HE-6 (induced by source paper "automated patch assessment for program repair at scale"):
  with members:
    - "how different is it between machine generated and developer provided patches an empirical study on the correct patches generated by automated program repair techniques"
    - "a comprehensive study of automatic program repair on the quixbugs benchmark"
    - "validation of automatically generated patches an appetizer"
    - "sequencer sequence to sequence learning for end to end program repair"
    - "bears an extensible java bug benchmark for automatic program repair studies"
    - "sorting and transforming program repair ingredients via deep learning code similarities"
    - "alleviating patch overfitting with automatic test generation a study of feasibility and effectiveness for the nopol repair system"
    - "empirical review of java program repair tools a large scale experiment on 2 141 bugs and 23 551 repair attempts"

Connected through hyperedge HE-7 (induced by source paper "empirical review of java program repair tools a large scale experiment on 2 141 bugs and 23 551 repair attempts"):
  with members:
    - "a comprehensive study of automatic program repair on the quixbugs benchmark"
    - "bears an extensible java bug benchmark for automatic program repair studies"
    - "sorting and transforming program repair ingredients via deep learning code similarities"
    - "alleviating patch overfitting with automatic test generation a study of feasibility and effectiveness for the nopol repair system"
    - "automatic software repair a bibliography"
    - "automatic repair of real bugs in java a large scale experiment on the defects4j dataset"
    - "ultra large repair search space with automatically mined templates the cardumen mode of astor"
    - "dissection of a bug dataset anatomy of 395 patches from defects4j"

Connected through hyperedge HE-8 (induced by source paper "astor exploring the design space of generate and validate program repair beyond genprog"):
  with members:
    - "a comprehensive study of automatic program repair on the quixbugs benchmark"
    - "alleviating patch overfitting with automatic test generation a study of feasibility and effectiveness for the nopol repair system"
    - "automatic repair of real bugs in java a large scale experiment on the defects4j dataset"
    - "ultra large repair search space with automatically mined templates the cardumen mode of astor"
    - "arja automated repair of java programs via multi objective genetic programming"
    - "an empirical analysis of the influence of fault space on search based automated program repair"
    - "identifying patch correctness in test based program repair"
    - "nopol automatic repair of conditional statement bugs in java programs"

Question: Please tell me which class the center node 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)