7 Matching Annotations
  1. Last 7 days
    1. Murine macrophage cell line J774A.1 (ATCC no. TIB-67) was maintained in phenol red free DMEM supplemented with 10% heat inactivated (45 min at 65°C) foetal bovine serum at 37°C in 5% C02 and 95% air. The cultures were sub-cultured every three days or at the attainment of 80 % confluency.
  2. Nov 2017
  3. Oct 2017
  4. Nov 2016
    1. Les fouilles se poursuivent pendant une décennie suivant la découverte, sous le regard des autorités jordaniennes mais nous avons peu de détails sur le déroulement de celles-ci.

      Est-ce qu’on sait pourquoi nous avons peu de détails sur le déroulement des fouilles? Était-ce en lien avec un climat politique particulier, ou une pratique de l'archéologie généralement négligée à cette époque, dans cette région?

  5. Feb 2016
    1. Recount stories, including fables, folktales, and myths from diverse cultures; determine the central message, lesson, or moral and explain how it is conveyed through key details in the text

      Students must read a wide variety of fiction story types, understand the moral, and explain what key details help identify it. I think stories about the greek gods would be fun and exciting for kids, possibly Hercules as a book and movie follow up.

  6. Oct 2015
    1. full loss function as coming from a Gaussian prior over the weight matrix WW, where instead of MLE we are performing the Maximum a posteriori (MAP) estimation. We mention these interpretations to help your intuitions, but the full details of this derivation are beyond the scope of this class.

      Can anyone provide resources where I can find this derivation? In particular, the derivation for the regularization term \(R(W)\) coming from a Gaussian prior on \(W\).

  7. Jan 2014
    1. I regret that the documentation does not focus on what is most relevant; by focusing on a largely irrelevant implementation detail, we enlarge the importance of that implementation detail and obscure the importance of what makes a value type semantically useful. I dearly wish that all those articles explaining what “the stack” is would instead spend time explaining what exactly “copied by value” means and how misunderstanding or misusing “copy by value” can cause bugs.

      Documentation should focus on semantically useful descriptions; another accompanying document (or annotation) can provide relevant implementation details upon request, but that deeper level of detail should be left out by default to avoid enlarging the importance of less relevant things.