Advances
in molecular genetics now allow the opportunity for international studies
such as ours to explore etiological hypotheses involving specific genes rather
than simple comparisons between races or ethnic groups. One of the most consistent
findings in AD research has been the association of the possession of the
apolipoprotein E (APOE) ∊4 allele to increased
susceptibility for AD.38 In contrast to reports
from other populations, we have found only a marginally significant association
between possession of the ∊4 allele and AD in
the African American population39 similar to
other study reports.40 In the Yoruba, we have
found no significant association between the possession of the ∊4 allele and dementia or AD in either the heterozygous
or homozygous states.41 As the frequencies
of the 3 major APOE alleles are almost identical
in the 2 populations, this variation in the strength of the association between ∊4 and AD may account for some of the differences in incidence
rates between the populations, although it is not likely to explain all of
it. It also raises the possibility that some other genetic or environmental
factor affects the association of the ∊4 allele
to AD and reduces incidence rates for dementia and AD in Yoruba.
https://jamanetwork.com/journals/jama/fullarticle/193548
Friday, November 8, 2019
there's an interesting list of references at the end of this article.
https://www.brainblogger.com/2017/09/15/environmental-factors-in-development-of-alzheimers-disease/
https://www.brainblogger.com/2017/09/15/environmental-factors-in-development-of-alzheimers-disease/
at
22:48
that was easier than i thought. i just had to delete the tokens.dat file and let the system rebuild the database. it's actually better now than it was before, because i'm not getting those annoying prompts...
i got a little distracted yesterday morning by my chromebook, which has developed some kind of corruption in the firmware. the battery appears to work according to the diagnostics, but the operating system doesn't seem to want to read it. i was hoping i could fix it easily by flipping a bit, but it looks like it's a more serious project. there's an entire component of the operating system that appears to be damaged...
it just means i need to keep it plugged in to use it, and that i have to use it in guest mode because it won't let me default to the pin. so, it's not catastrophic. but i want to fix it. i was hoping i could do it quickly in the morning, then take a nap before i went out, but i just learned it's going to be a project. so, i'm going to put that aside for a few days, although i'd like to get a handle on it before i go to toronto.
last night didn't work out as intended, but i'm glad i figured it out before i got stuck. i went to buy some tickets from the terminal, and they told me the tunnel was closing for the night. so, my plan to hit the concerto and the noise rock show was foiled; i stayed in windsor, instead. i'll do up a review in a bit, but it's going to be sort of short and not that exciting.
i was home late, ate, showered and slept all day....
how is the smell in here? i did try to turn the fan off this morning, but i've got it back on tonight. it's a smoky kind of smell, and i might be tempted to conclude somebody was smoking, but i've learned that it might be remnant complications from the sewer gas. i don't know, really. i know that i had to turn the fan back on, and i'll try again in a few more days. i can't smell the sewer in the closet, but the heat has been on, and i know that resolves it, regardless. the smell coming out of the fixtures has been getting better but hasn't resolved itself.
so, i need to spend the night doing what i intended to do yesterday morning, which is reassembling this week's rambling. and, then, i intend to get back to those liner notes, and get them done with by the end of the weekend.
i got a little distracted yesterday morning by my chromebook, which has developed some kind of corruption in the firmware. the battery appears to work according to the diagnostics, but the operating system doesn't seem to want to read it. i was hoping i could fix it easily by flipping a bit, but it looks like it's a more serious project. there's an entire component of the operating system that appears to be damaged...
it just means i need to keep it plugged in to use it, and that i have to use it in guest mode because it won't let me default to the pin. so, it's not catastrophic. but i want to fix it. i was hoping i could do it quickly in the morning, then take a nap before i went out, but i just learned it's going to be a project. so, i'm going to put that aside for a few days, although i'd like to get a handle on it before i go to toronto.
last night didn't work out as intended, but i'm glad i figured it out before i got stuck. i went to buy some tickets from the terminal, and they told me the tunnel was closing for the night. so, my plan to hit the concerto and the noise rock show was foiled; i stayed in windsor, instead. i'll do up a review in a bit, but it's going to be sort of short and not that exciting.
i was home late, ate, showered and slept all day....
how is the smell in here? i did try to turn the fan off this morning, but i've got it back on tonight. it's a smoky kind of smell, and i might be tempted to conclude somebody was smoking, but i've learned that it might be remnant complications from the sewer gas. i don't know, really. i know that i had to turn the fan back on, and i'll try again in a few more days. i can't smell the sewer in the closet, but the heat has been on, and i know that resolves it, regardless. the smell coming out of the fixtures has been getting better but hasn't resolved itself.
so, i need to spend the night doing what i intended to do yesterday morning, which is reassembling this week's rambling. and, then, i intend to get back to those liner notes, and get them done with by the end of the weekend.
at
19:29
we'll talk soon. i want to figure this out once and for all, first.
the key activates. it's fine. i got it from school, i think. but, my haphazard workaround has created some kind of access request error - system files still belong to the removed account.
i don't want to just take ownership of the whole drive. i want to figure out the precise concern.
for now, this is priceless. stupid windows...
the key activates. it's fine. i got it from school, i think. but, my haphazard workaround has created some kind of access request error - system files still belong to the removed account.
i don't want to just take ownership of the whole drive. i want to figure out the precise concern.
for now, this is priceless. stupid windows...
at
18:24
Subscribe to:
Posts (Atom)