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: "software developers moods emotions and performance"
  Abstract: HIGH-TECH COMPANIES like Google, Facebook, and Supercell are well known for their perks, such as having fun things to do and good food to eat during working hours. The underlying assumption is that “happy software developers perform better than unhappy ones.” However, does any evidence support this? Evidence is especially desirable for those who don’t work in these “fun” companies: the paradisiacal environment usually described by tech-giant workers fuels horror stories told by frustrated developers on a daily basis (see thedailywtf.com and clientsfromhell. net). It seems that managers need to be reminded of the “obvious” claim that happy developers work better. Scientifi c articles have long claimed that the best way to improve software developers’ performance is by focusing on people1 and that people trump process.2 Software development is deeply dominated by human factors.3 Software development is complex, purely intellectual, and accomplished through cognitive processing abilities.4 No matter how much we want to believe that software construction processes can be engineered, software developers are creative human beings and they need to make sense of unpredictable, turbulent environments.5 Sense-making processes are infl uenced by individuals’ affects (emotions and moods),6 just as cognitive processes are tied to problem-solving performance.7 In the software engineering research arena, very few studies have been conducted into how developers feel or the consequences of their feelings. This article summarizes existing psychology and software engineering studies conducted on how software developers experience affects and demonstrates how practitioners are calling for such studies to be conducted.

Connected through hyperedge HE-1 (induced by source paper "measurement of interpersonal trust in global software development slr protocol"):
  with members:
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-2 (induced by source paper "happiness and the productivity of software engineers"):
  with members:
    - "what happens when software developers are un happy"
    - "on the unhappiness of software developers"
    - "how do you feel developer an explanatory theory of the impact of affects on programming performance"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-3 (induced by source paper "what happens when software developers are un happy"):
  with members:
    - "unhappy developers bad for themselves bad for process and bad for software product"
    - "consequences of unhappiness while developing software"
    - "on the unhappiness of software developers"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "how do you feel developer an explanatory theory of the impact of affects on programming performance"
    - "the affect of software developers common misconceptions and measurements"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"

Connected through hyperedge HE-4 (induced by source paper "consequences of unhappiness while developing software"):
  with members:
    - "unhappy developers bad for themselves bad for process and bad for software product"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "how do you feel developer an explanatory theory of the impact of affects on programming performance"
    - "the affect of software developers common misconceptions and measurements"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-5 (induced by source paper "on the unhappiness of software developers"):
  with members:
    - "consequences of unhappiness while developing software"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "how do you feel developer an explanatory theory of the impact of affects on programming performance"
    - "the affect of software developers common misconceptions and measurements"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-6 (induced by source paper "unhappy developers bad for themselves bad for process and bad for software product"):
  with members:
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "how do you feel developer an explanatory theory of the impact of affects on programming performance"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-7 (induced by source paper "towards the assessment of stress and emotional responses of a salutogenesis enhanced software tool using psychophysiological measurements"):
  with members:
    - "unhappy developers bad for themselves bad for process and bad for software product"
    - "at ease with your warnings the principles of the salutogenesis model applied to automatic static analysis"
    - "how do you feel developer an explanatory theory of the impact of affects on programming performance"

Connected through hyperedge HE-8 (induced by source paper "towards a theory of affect and software developers performance"):
  with members:
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "in need of creative mobile service ideas forget adults and ask young children"
    - "a framework for systematic analysis of open access journals and its application in software engineering and information systems"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"
    - "the role of emotions in contributors activity a case study on the gentoo community"
    - "are happy developers more productive"
    - "commitment nets in software process improvement"

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)