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: "unhappy developers bad for themselves bad for process and bad for software product"
  Abstract: Recent research in software engineering supports the "happy-productive" thesis, and the desire of flourishing happiness among programmers is often expressed by industry practitioners. Recent literature has suggested that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness of developers due to its negative impact. However, possible negative effects of unhappiness are still largely unknown in the software development context. In this paper, we present the first results from a study exploring the consequences of the unhappy developers. Using qualitative data analysis of the survey responses given by 181 participants, we identified 49 potential consequences of unhappiness while developing software. These results have several implications. While raising the awareness of the role of moods, emotions and feelings in software development, we foresee that our classification scheme will spawn new happiness studies linking causes and effects, and it can act as a guideline for developers and managers to foster happiness at work.

Connected through hyperedge HE-1 (induced by source paper "what happens when software developers are un happy"):
  with members:
    - "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"
    - "software developers moods emotions and performance"

Connected through hyperedge HE-2 (induced by source paper "sentiment polarity detection for software development"):
  with members:
    - "bootstrapping a lexicon for emotional arousal in software engineering"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "recommending insightful comments for source code using crowdsourced knowledge"
    - "nrc canada building the state of the art in sentiment analysis of tweets"
    - "efficient estimation of word representations in vector space"
    - "distributed representations of words and phrases and their compositionality"
    - "a computational approach to politeness with application to social factors"
    - "machine learning in automated text categorization"

Connected through hyperedge HE-3 (induced by source paper "consequences of unhappiness while developing software"):
  with members:
    - "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"
    - "software developers moods emotions and performance"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-4 (induced by source paper "towards the assessment of stress and emotional responses of a salutogenesis enhanced software tool using psychophysiological measurements"):
  with members:
    - "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"
    - "software developers moods emotions and performance"

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)