ialsa / ialsa-2018-amsterdam Goto Github PK
View Code? Open in Web Editor NEWMutistate models of physical decline: Coordinated analysis with replication
Mutistate models of physical decline: Coordinated analysis with replication
Present: @GracielaMuniz, @annierobi, @emielhoogendijk , @jochinho , Judith
We inherit the methodology from iasla-2016-amsterdam
and iasla-2017-amsterdam
and focus on measures of physical performance: hand grip and speed gait
maybe:
in-person
meeting. There will be an IALSA meeting in January in Chicago, so it might be easier to fly the European partners over.Looking back at 2016
and 2017
, what does the writer need to organize the manuscript? We started making bullets:
gait
and grip
that would operationally define physical impairment
What writer needs
list and prepare a draft report using MAP data from ialsa-2017-amsterdam
with intent to automate some of the outputDear all,
Some information for the TC tomorrow:
I have been reading the literature about cut-offs with regard to slow gait speed and weak grip strength. Most articles from the frailty field use the frailty criteria of Fried et al (2001), which includes gait speed and grip strength. Everybody copies their cut-offs, which is not completely logic as they were based on the lowest quintiles from one database, the Cardiovascular Health Study (height/sex specific for gait speed, and BMI/sex specific for grip strength, see the article in the attachment). We could follow the approach of Fried (either using their cut-offs, or derive cut-offs from lowest quintiles in our datasets) or we could go for other established measures, like a general gait speed cut-off (not taking into account sex and height).
For gait speed we can choose two approaches:
For grip strength there are no general cut-offs, as far as I know:
I don`t know if we combine gait speed and grip strength in one paper? I would prefer to focus on gait speed first (as there is now a lot of literature about the slow gait speed as early signal of motoric problems related to starting dementia, see for example the article of Del Campo in the attachment – and also in geriatrics slow gait speed is seen as the best indicator of declining health). What would be interesting is to compare the 0.6 m/sec cut-off with the lowest quintile approach, to see whether it gives consistent results across studies. This could result in a paper that is interesting for JAGS (Journal of the American Geriatrics Society).
As it is an extension of our previous analyses, all the other variables should remain the same:
· Age
(time dependent – we have to discuss about the centering)
· Sex
(same as before)
· Educational level
(continuous, centering we have to discuss)
· State
variable (same as before, based on MMSE: no cognitive impairment, mild cognitive impairment, severe cognitive impairment and death)
In addition to inherited variables we need:
· Gait speed in seconds
(please check the distance measured in your study, as well as the protocol: normal pace or rapid pace)
· Height in cm
· Grip strength (if available) in Kg
(please check which dynamometer was used and in which position the grip strength was measured)
· Body Mass Index
(body weight in kilograms divided by height in meters squared).
We may discuss if we need to adjust for comorbidity (number of chronic diseases) or not. But in our previous analyses we also did not control for many covariates, so maybe it is not necessary.
I think we also don`t need income. Educational level is more important.
Cut-offs for gait speed (sex/height specific or not) is still to be determined.
Some points for discussion:
(1). Convention for model and submodels nomenclature
(2). Does everyone have physical activity?
(3). Do we separate analyses by gender?
(4). What are the specific instruction for age*gender specific cutoffs for gait?
(5). What should be the method for converting time-variant measures to time-invariant?
Here's the solution Ardo prepared for selecting those individuals who have a valid observation of gait
between ages 68 and 72 (inclusive)
dta <- ds_valid %>% dplyr::select(-firstobs)
subjects <- unique(ds_valid$id)
library(dplyr)
library(elect)
# dta <- ELECTData
# subjects <- unique(dta$id)
for(i in 1:length(subjects)){
dta.i <- dta[dta$id==subjects[i],]
if(nrow(dta.i)<=2){print(subjects[i])}
}
dta %>% glimpse()
# Subselect:
bound <- c(68,72)
count <- 0
for(i in 1:length(subjects)){
select <- 0
dta.i <- dta[dta$id==subjects[i],]
if(dta.i$age[1]< bound[2]){
ddta.i <- dta.i[dta.i$age>bound[1],]
if(nrow(ddta.i)>1){
select <- 1; print(i)
select <- 1 ; print (i)
firstobs <- rep(0, nrow(ddta.i))
firstobs[1] <- 1
ddta.i <- cbind(ddta.i, firstobs = firstobs)
}
}
if(select==1 & count==0){
ddta <- ddta.i
count <- count +1
}
if(select==1 & count>0){
ddta <- rbind(ddta,ddta.i)
count <- count+1
}
}
hist(ddta$age[ddta$firstobs == 1])
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.