10 Matching Annotations
  1. Jul 2026
    1. SK Hynix filed to raise up to 45.45 trillion won (~$29.4B) via a Nasdaq ADR listing

      近300亿美元的巨额募资,反映了 AI 算力基础设施对高带宽内存(HBM)的极端渴求。在投资者追捧 AI 存储芯片的背景下,这种规模的上市不仅是资金的角逐,更暗示着全球半导体供应链正在围绕 AI 算力需求进行深度的资本重构。

  2. May 2026
    1. By predicting these unified tokens, it effectively leverages diverse human data to achieve state-of-the-art data efficiency and robust out-of-distribution (OOD) generalization.

      这一实验结果展示了UniT在利用人类数据实现高效和鲁棒泛化方面的潜力,为数据效率和泛化能力提供了新的标准。

  3. Aug 2022

    Tags

    Annotators

  4. Dec 2020
  5. Jun 2020
  6. May 2020
    1. It’s useful to remember that under GDPR regulations consent is not the ONLY reason that an organization can process user data; it is only one of the “Lawful Bases”, therefore companies can apply other lawful (within the scope of GDPR) bases for data processing activity. However, there will always be data processing activities where consent is the only or best option.
  7. Apr 2020
  8. Jan 2014
    1. A key component of data management is the comprehensive description of the data and contextual information that future researchers need to understand and use the data. This description is particularly important because the natural tendency is for the information content of a data set or database to undergo entropy over time (i.e. data entropy ), ultimately becoming meaningless to scientists and others [ 2 ].

      I agree with the key component mentioned here, but I feel the term data entropy is an unhelpful crutch.

    1. Researchers may be underestimating the need for help using archival storage systems and dealing with attendant metadata issues.

      In my mind this is a key challenge: even if people can describe what they need for themselves (that in itself is a very hard problem), what to do from the infrastructure standpoint to implement services that aid the individual researcher and also aid collaboration across individuals in the same domain, as well as across domains and institutions... in a long-term sustainable way is not obvious.

      In essence... how do we translate needs that we don't yet fully understand into infrastructure with low barrier to adoption, use, and collaboration?