Kyle Husmann

Newbie here. @hesxenon what you describe as "desired behavior" is how I naively expected the imports to work. Until I found this issue I was pretty confused trying to follow...

Looks like I'm late to the party here, but wanted to join the convo if there's still time before this interface is solidified in v1.0. My plugin use case is...

Ok, I'm taking a slightly different approach, which I think is sort of close to the in-memory _metadata table idea. I'm using a startup hook to load metadata / other...

Awesome, thanks @brandonrobertz ! The plugin is close, but looks like it only grabs remote metadata, is that right? Instead what I'm wanting is to grab metadata embedded in the...

Thanks for taking the time to reply @brandonrobertz , this is really helpful info. > See "Many small queries are efficient in sqlite" for more information on the rationale here....

Ah, sorry, I didn't get what you were saying you the first time. Using _metadata_local in that way makes total sense -- I agree, refreshing metadata each cell was seeming...

As a user I only use # of evals to estimate the speed and check how long it's been running. So maybe something like this? `[hh:mm:ss] MxComputeGradientDescent(SLSQP) 40eval/sec LL=318876 ΔLL=-1.955e+04`

Related: when I'm running models from non-interactive R processes, I can't seem to get progress outputs even when I run with silent=F (is there another option I'm missing?) What would...

> Yeah, OpenMx conditions on `interactive()`. Why do you want non-interactive progress output? I run big batches of large models on a cluster through scripts that call R in non-interactive...

> Wouldn't it be better to always enable checkpointing? I would, if mxTryHard() supported checkpointing (#282). So maybe that's the larger issue here. Still though, sometimes it is nice to...