Dear all,
Hope everyone is staying well in this difficult time.
I am bootstrapping standard errors of the estimates that are obtained from the following line of code:
npregress kernel price unitsize i.floor i.byear_lump, estimator(linear) kernel(gauss) dkernel(li)
Bootstrapping the standard error (using wild bootstrap) is straightforward, except that it takes a long time for each iteration to terminate.
I am running multiple instances of my code on a server, but the server imposes a time limit on how each instance can be run on it (24 hours), and it turned out that the code takes longer than that to terminate.
Other than reducing the number of observations (currently 72000, and the code terminates after 79000 seconds on my desktop), is there any way to get around the time limit, e.g., have Stata store the current state of the algorithm right before the time limit force quits the program, so that the Stata can restart from there when the code is run again?
Any advice would be greatly appreciated,
Thanks,
Sam
Related Posts with Getting around the time limit imposed by the server
Implement Multinomial Logit Model using ml commandI would like to implement multinomial logit model using maximum likelihood command to generate the s…
Merging two databases. With different dates. Best method?Dear members, These days I am working on my (master) thesis and I am working with Stata in order t…
panelsubmatrix(): 3301 subscript invalidI use stata15 and I write Code: xsmle INDEX CREDDEV CHEXCHRATE UNINF, wmat(Z) model(sdm) and I ge…
How to use "/" in StataHi everyone, I would like to know how to build a code that lets me display the following data: Ind…
is it possible to do a repeated Measures ANOVA without case identifierHi all, I am currently using a Qualtrics platform survey to measure the perceived social consensus …
Subscribe to:
Post Comments (Atom)
0 Response to Getting around the time limit imposed by the server
Post a Comment