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 "when can helper node selection improve regenerating codes part ii an explicit exact repair code construction"):
  Abstract: Part I of this work answered the following fundamental question: Under and only under what (n,k,d) values does proactively choosing the helper nodes improve the storage-bandwidth tradeoff of regenerating codes (RCs)? A critical component of the achievability results in Part I is a low-complexity helper selection solution, termed the family helper selection (FHS) scheme. In Part I, FHS was proved to be optimal or weakly optimal (depending on the underlying scenario) based on the assumption that as long as the minimum min-cut value of FHS is no less than the file size, we can always find a distributed storage code that can reconstruct the original file. This work relaxes this assumption by providing an exact-repair code construction that attains the minimum-bandwidth-regenerating (MBR) point of FHS, previously calculated/predicted only by the min-cut analysis in Part I. As an outcome, for the MBR points, FHS is indeed optimal or weakly optimal under various scenarios. #R##N#In addition to closing the loop of the graph-based study in Part I, the proposed construction can also be viewed as a generalization of the existing fractional repetition (FR) codes. FR codes are exact-repair codes that admit the highly-desirable repair-by-transfer property. However, the unique construction of FR codes limits its application to a restricted set of (n,k,d) system parameters. In contrast, our new construction, termed the generalized FR (GFR) codes, can be applied to arbitrary (n,k,d) values. Our GFR codes retain most of the practical benefits of FR codes, i.e., being exact-repair and being almost repairable-by-transfer.

Includes members:
  Member "optimal fractional repetition codes based on graphs and designs":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "optimal fraction repetition codes for access balancing in distributed storage")
  Member "replication based storage systems with local repair":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "bounds on fractional repetition codes using hypergraphs")
  Member "explicit mbr all symbol locality codes":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "the complete hierarchical locality of the punctured simplex code")
  Member "distributed storage codes with repair by transfer and nonachievability of interior points on the storage bandwidth tradeoff":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "enabling optimal access and error correction for the repair of reed solomon codes")
  Member "interference alignment in regenerating codes for distributed storage necessity and code constructions":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "conditional disclosure of secrets a noise and signal alignment approach")
  Member "repairable replication based storage systems using resolvable designs":
    also connected through other hyperedges:
      - Hyperedge HE-6 (induced by source paper "optimal fraction repetition codes for access balancing in distributed storage")
  Member "scalable constructions of fractional repetition codes in distributed storage systems":
    also connected through other hyperedges:
      - Hyperedge HE-7 (induced by source paper "on universally good flower codes")
  Member "optimal exact regenerating codes for distributed storage at the msr and mbr points via a product matrix construction":
    also connected through other hyperedges:
      - Hyperedge HE-8 (induced by source paper "enabling optimal access and error correction for the repair of reed solomon codes")

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.IT(Information Theory)