94 Matching Annotations
  1. Sep 2022
  2. Aug 2022
  3. Jul 2022
  4. May 2022
    1. "I didn't fully understand it at the time, but throughout my time as a freshman at Boston College I've realized that I have the power to alter myself for the better and broaden my perspective on life. For most of my high school experience, I was holding to antiquated thoughts that had an impact on the majority of my daily interactions. Throughout my life, growing up as a single child has affected the way am in social interactions. This was evident in high school class discussions, as I did not yet have the confidence to be talkative and participate even up until the spring term of my senior year."

  5. Apr 2022
    1. 人生低谷,全世界都看低你,你也不能看轻自己。 因为只有抬得起头,你才能在迷惘中找到出路。

      save

  6. Aug 2021
  7. Jun 2021
    1. There were attempts to simplify this setup by building specific browsers (such as capybara-webkit and PhantomJS) providing such APIs out-of-box, but none of them survived the compatibility race with real browsers.
  8. Apr 2021
    1. Due to player actions not landing on the beat or being relevant to the background music, this 'rhythm' game falls short of it's goals. No feedback for early or late actions also diminishes the game.
    2. Piano Cat is a challenging rhythm-based platformer game where you [...] jump to the beat [...].No, no, no, just no. This game has nothing to do with rhythm or doing something in sync to the music. If you try to do that, you will fail, a lot. In order to beat the stages you have to mute or ignore the music, ignore the obstacles and only look out for the buttons you have to press. When they light up green, you press the button. This means that you have to press them always too early to the action, ahead of time. If you try to time it to the music, it will be too late and not count. If you are good in these kind of games, this will totally throw you off here.The graphic are nice, the music is ok, but it does a terrible job in having rhythm based gameplay.
  9. Feb 2021
    1. You’re allowed to blame us for a terrible developer experience in Trailblazer 2.0. It’s been quite painful to find out which step caused an exception. However, don’t look back in anger! We’ve spent a lot of time on working out a beautiful way for both tracing and debugging Trailblazer activities in 2.1.
    1. Around 2 years ago I decided to end the experiment of “TRB PRO” as I felt I didn’t provide enough value to paying users. In the end, we had around 150 companies and individuals signed up, which was epic and a great funding source for more development.
  10. Oct 2020
  11. May 2020
    1. Given the massive amount of stars it had acquired on Github and the fairly quick and easy setup, it seemed very promising. When it comes down to its isomorphic functionality, it’s hard to match. But when it we started using the static export features, we were dropped on our faces with a very ungraceful transition from isomorphic to static that came with a cold side of faulty hot-reloading, strange routing strategies and highly bloated bundles:
  12. Jun 2019
    1. “Because the bully had no prior record of bullying, and even though there were so many different days and incidents of physical assault, it was treated as a one-time offense, and for a one-time offense you just get a short talk and a call home,”

      In order for suspension and expulsion, there must be multiple offense. In this case, there are witnesses and a confession, but that is not enough. Even though there were many different days and incidents of physical assault this is considered a one-time offense? A short talk and a phone call home is the consequences of a death threat and physical assault? Where is the importance of bullying would not be tolerated? Where is the importance of ensuring the victim's safety? This is why this whole system fail to tackle on the issue of bullying. The limit of what the school can do is unjust. How is that resolved? The victim and their family would still feel unsafe, fear, and paranoia.

  13. Nov 2016
    1. t(27) = 0.41, p<0.05;

      Is this t test correct? The t statistic and degrees of freedom you've provided don't seem to be consistent with any given p-value given.

    2. Did you receive permission to use field samples?

    3. Have you explained what your exclusion and inclusion criteria were?

    4. Have you considered including ORCIDs for every author? Although not compulsory, ORCIDs are a good way of making sure authors get credit for your work by distinguishing them from every other researcher in the world.

    5. Have you included the term 'Randomised Trial' in your title?

    6. Have you considered identifying the animals you used using a resource identifier? Although not compulsory, resource identifiers remove any ambiguity over which animals you used, and can make your work more discoverable.

    7. Have you included a section where you explain author contributions? You should mention each author by their initials and explain how they contributed to the work.

    8. Have you used the STARD reporting guideline? If so, you should say so in your methods.

    9. t = 0.81,

      Have you reported the degrees of freedom for this t-test?

    10. t= 1.01,

      Have you reported the degrees of freedom for this t-test?

    11. t = 2.31,

      Have you reported the degrees of freedom for this t-test?

    12. References

      Should your references follow a numerical system?

    13. Kendall et al., 2005)

      You have referenced this citation

    14. Have you explained whether participants and personnel were blinded?

    15. bstract

      Have you included a 'Results' subsection in your abstract?

    16. Van der Werf YD, Witter MP, Groenewegen HJ (2002) The intralaminar and midline nuclei of the thalamus. Anatomical and functional evidence for participation in processes of arousal and awareness. Brain Res Brain Res Rev 39:107-140.

      This reference is cited

    17. Minamimoto T, Hori Y, Kimura M (2005) Complementary process to response bias in the centromedian nucleus of the thalamus. Science 308:1798-1801.

      This reference is cited

    18. Matsumoto N, Minamimoto T, Graybiel AM, Kimura M (2001) Neurons in the thalamic CM-Pf complex supply striatal neurons with information about behaviorally significant sensory events. J Neurophysiol 85:960-976.

      This reference is cited

    19. Kinomura S, Larsson J, Gulyas B, Roland PE (1996) Activation by attention of the human reticular formation and thalamic intralaminar nuclei. Science 271:512-515.

      This reference is cited

    20. Have you included a word count?

    21. Did you receive ethical approval for this study?

    22. This analysis revealed that the response to CL axon stimulation was consistently larger in amplitude than the response to Pf for both direct and indirect pathway MSNs (direct pathway: t(27) = 1.98, p<0.05).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    23. Secondly, the cortical response recovers more quickly than the thalamic response after both 10 Hz and 20 Hz stimulation (ratio of response to first pulse: 10 Hz; cortical 0.87 ± 0.05, vs. thalamic 0.57 ± 0.05, 20 Hz; cortical, 0.90 ± 0.12 vs. t(72) = 3.07, p<0.05).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    24. We found that the paired-pulse ratio (PPR) for afferents from CL are facilitating (t(55) = 2.02, p<0.05), whereas those from Pf are depressing (t(27) = 3.12, p<0.05).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    25. We found that CL synapses are dominated by AMPA receptor-mediated currents, whereas Pf synapses are dominated by NMDA receptor-mediated currents (t(27) = 5.31, p<0.01).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    26. Furthermore, the analysis revealed that the response to CL axon stimulation was larger in amplitude on direct pathway neurons (direct pathway: t(27) = 1.99, p<0.05; Table 1).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    27. Cortical synapses exhibit an NMDA/AMPA ratio in between those of CL and Pf synapses and dominated by NMDA receptor-mediated currents (mean NMDA/AMPA ratio for cortical: t(27) = 2.66, p<0.05).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    28. However, the same protocol applied to CL synapses did not lead to any change in the amplitude of evoked EPSPs (t(27) = 0.41, p<0.05; Figure 5A).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    29. The average amplitude of response following CL axon stimulation was 66.3 ± 13.5 pA (stim strength; 450 mW; n = 16), whereas those following Pf axon stimulation were significantly smaller at 30.7 ± 4.1 pA (stim strength: 980 mW; t = 0.81, p<0.05).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    30. The Pf response is significantly depressing following both the 10 and 20 Hz trains and the rate of recovery was the least of all three responses (t(44) = 3.10, p<0.05; Figure 3B).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    31. Whereas all responses depress eventually, only the responses of CL inputs are facilitating for the first few spikes during both 10 and 20 Hz stimulation CL (t(72) = 1.73, p<0.05;

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    32. We found that the EPSC properties for CL and Pf synapses using this stimulation strength are remarkably similar, with some small differences in that CL EPSCs were larger in amplitude (t = 2.31, p<0.05) and Pf EPSCs slightly longer in duration (t= 1.01, p=0.02).

      It's often good practice to accompany every p value with a confidence interval, or another measure of precision.

    33. Figure 1A,

      Have you included figures in this file?

    34. Have you included an email address for every author?

    35. Have you used and cited the CARE guidelines for reporting case studies? If so, you should say so in your methods section.

    36. Did you get permission to use fossils? Who from? And are the fossils publically available?

    37. Have you used the PRISMA guidelines for reporting systematic reviews? If so, you should say so in your methods section.

    38. t = 2.31,

      Have you stated that your data meets the assumptions for an t-test?

    39. Have you used the MOOSE guidelines for reporting systematic reviews of observational studies? If so, you should state so in your methods.

    40. Have you included a participant flow diagram? This is generally highly recommended for randomised trials.

    41. Have you included a section called Ethical Approval?

    42. bstract

      Have you included a 'Purpose' subsection in your abstract?

    43. Have you used the ENTREQ reporting guidelines? If so, you should say so in your methods.

    44. Figure 4: NMDA / AMPA receptor ratio at CL, Pf and cortical synapses on MSNs Postsynaptic excitatory currents were recorded from MSN held at +40 mV to reveal both AMPA receptor and NMDA receptor-mediated currents or just AMPA receptor-mediated currents in the presence of d-AP5. Each excitatory input has a distinct ratio of currents mediated by either receptor type. CL synapses on MSNs exhibit predominant AMPA receptor-mediated currents. Pf synapses on MSNs exhibit predominant NMDA receptor-mediated currents. Cortical inputs similarly exhibit predominant NMDA receptor-mediated expression, but to a lesser degree than Pf. The histogram shows the mean (± SEM) NMDA/AMPA receptor ratio for each synapse. Sourced from some citation

      You've mentioned this figure in the article body

    45. Have you said who funded this research? Make sure you used the right name.

    46. Have you explained how you randomly allocated subjects into experimental groups?

    47. When writing your manuscript, did you use the CONSORT guidelines for randomised trials? If so, you should say so in your methods section.

    48. Have you included a section called "Consent for Publication"? If you are reporting individual level data you must obtain consent. Otherwise, you should write "Not Applicable"

    49. Have you used and the REMARK reporting guidelines? If so, you should say so in your methods section

    50. Have you used the ARRIVE guidelines for reporting animal research? If so, you should mention it in your methods.

    51. Did participants give informed consent?

    52. Have you said which Ethical Review Board gave you ethical approval?

    53. Does your work adhere to the ARVO statement?

    54. P. Bolam

      Have you provided an affiliation for this author? They don't seem to a member of any institution that you've mentioned.

    55. P. Kossilo*

      Have you provided an affiliation for this author? They don't seem to a member of any institution that you've mentioned.

    56. J. Harwood*

      Have you provided an affiliation for this author? They don't seem to a member of any institution that you've mentioned.

    57. T. Ellender,

      Have you provided an affiliation for this author? They don't seem to a member of any institution that you've mentioned.

    58. Have you used the STROBE reporting guideline? If so, you should say so in your methods.

    59. bstract

      Have you included a 'Methods' subsection in your abstract?

    60. p<0.05;

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    61. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    62. p<0.01)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    63. p<0.05;

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    64. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    65. p<0.05;

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    66. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    67. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    68. p<0.05;

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    69. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    70. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    71. p<0.05)

      It's good practice to report p values exactly. So a p value of 0.46 would be reported as p = .46, not p < .05. An exception is for p values less than 0.001, which can always be reported as p < .001.

    72. Have you explained how you decided what sample size you needed?

    73. Table 1

      Have you included a short legend for this table?

    74. bstract

      Have you included a 'Conclusions' subsection in your abstract?

    75. Have you included a section called "Declarations"?

    76. : t(27) = 1.98, p<0.05)

      Have you justified using a 1 tailed t-test? This p-value is not consistent with a 2-tailed t-test.

    77. Have you used the TRIPOD reporting guideline? If so, you should say so in your methods.

    78. Have you used the SRQR reporting guideline? If so, you should say so in your methods.

    79. Have you included your trial registration ID? Generally this is compulsory for clinical trials, and it should go at the end of your abstract. You should also include the registry name and date of registration. If your trial was registered retrospectively you should state that too.