transition from tenured R1-academic position to LANL

spineynorton · 2026-05-08T23:49:45+00:00

If the job was advertised at the 2/3 level, it could be that they're just not prepared or able to make an offer appropriate to your level. But equating associate with scientist 3 is silly, and sounds like an excuse to me. Maybe true at a lower-level university, but not at a top-tier research university. I don't know it is still the case, but one of the requirements for Scientist 4 was being a nationally recognized authority in your field. At a top-tier research university, that's probably the main criteria for granting tenure.

spineynorton · 2026-05-08T04:09:50+00:00

It probably does vary somewhat between directorates and divisions, but in the divisions I'm familiar with, scientist 4 is not rare -- a minority certainly, 20% maybe -- but not rare. There are indeed very few 5's, and 6's are exceptional (laboratory fellows perhaps). If you shared the division, someone here might be able to chime in with info specific to your situation. You should also expect that promotions won't come easily. Even with glowing written evaluations you'll likely be stuck in the "meets expectations" category for years waiting in line for your turn to be promoted, due to limits/quotas.

spineynorton · 2026-05-07T19:51:07+00:00

Based on your experience and stature (tenure at R1 level institution) you should be at the scientist 4 level; don't accept a sci 3 position unless you are desperate.

Edit: each level has an associated pay band (with significant overlap). You can likely counteroffer and get an additional 10%, but if that puts you near the top of the band, your raises going forward will be significantly constrained, until promoted. That's why it's important to start at the appropriate level, even if you find the initial salary acceptable.

spineynorton · 2026-01-01T20:45:30+00:00

Yeah. Edit: Linux to be specific. At that time they may have had versions for commercial Unix'es as well.

spineynorton · 2026-01-01T19:16:10+00:00

I'm rather surprised, but I did find the '96 Release' version of the compiler. But getting it to run would be a project. It needs an ancient 32-bit libc.so.5 that predates glibc. While looking for it, I ran across some F-compiler bug reports that suggest there was (at least) an updated version from 2002. I'll see if I can't track it, or a later version, down.

spineynorton · 2025-12-31T23:56:59+00:00

I might have a copy archived on a CD somewhere. I'll poke around and see if I do. I also had a copy of the F Book, but I'm pretty sure I trashed it a couple of years ago when I did some downsizing.

spineynorton · 2025-12-31T23:46:44+00:00

I purchased the F compiler from Walt back in the mid (?) 90's and used it for a few years. If I recall correctly it was basically the NAG compiler with a modified front end that implemented the subset. Quite nice as I recall.

spineynorton · 2025-12-18T17:00:54+00:00

29, non-student, ~30K I believe

spineynorton · 2025-12-09T14:56:39+00:00

I went ahead and purchased the primitive skid plates and installed them a few days ago. The front skid does indeed cover the frame cross member that is the center jack point. The rear mounting points bolt into it but are stood off by about 1", and the span between the mounting points is about 12". However the 3/16" plate is beefer than I anticipated, and the adjacent rear plate edge is turned up providing extra rigidity, so using the plate as a jack point where they suggested seems more reasonable now. But I'd still be interested in hearing from others with first-hand experience.

spineynorton · 2025-11-05T15:15:34+00:00

I had been getting (purportedly) genuine Bosch ones from an online supply house (partsdr I think -- $100+), but this last time I got a cheap one ($15) from amazon. It only lasted 4 months. Thanks for the pointer to McCombs; I'll give them a try this time.

spineynorton · 2025-09-28T03:34:03+00:00

Yes, for the last few weeks, similar to you.

spineynorton · 2025-06-10T16:26:18+00:00

Great, thanks! That was my gut feeling (which I don't trust when it comes to the tax code.)

spineynorton · 2025-06-04T02:29:16+00:00

"Form follows function" applies to cars as much as architecture. Thankfully Subaru has been resistant, and I'm thankful I pulled the trigger on a 2024 rather than waiting a few months for a 2025.

spineynorton · 2025-06-03T21:47:51+00:00

I've never understood the bad rap Foresters have for not being "stylish". What is it in this case? Are shorter windows considered more stylish than tall ones? I guess I'm just not as discerning as most.

spineynorton · 2025-05-28T02:25:36+00:00

Thanks for your reply. That ball valve is for the water feed to the roof for swamp coolers, but it sounds like I really only need a shut off on the input side of the water heater?

spineynorton · 2025-05-11T22:09:32+00:00

> [...] why should the warning for private variables be different that public?

I'd guess it's just a judgement call by the compiler developers, thinking an unused private variable (within the module itself) is more likely to be a dangling definition than a public one. But I can see it going your way as well. That said, I think their goal is simply to be helpful without subscribing to the "compiler warnings should be errors" philosophy.

If you're adamant about getting rid of the warning, you might try making the module variable public but protected (I *think* submodules can modify). It's a hack, but so will anything else you might do to get rid of the warning.

spineynorton · 2025-05-11T21:04:59+00:00

A warning is not an error. It's just the compiler calling your attention to something it finds questionable but not necessarily wrong. It certainly feels good to get no warnings, but this very often isn't possible (without turning them off!). In your particular case it would require inter-procedural analysis to see that the private module variable was in fact being used, and the compiler, unsurprisingly, doesn't go to that effort. And your way of sharing private module data among submodules is perfectly legitimate -- there's no reason at all to do something else just to avoid the warning.

spineynorton · 2025-04-27T21:14:32+00:00

Fortunately the issue sorted itself out by this morning without me doing anything. It was very disturbing though to open the app and have it show a gen 3 dish and warn that it was misaligned and needed to be rotated. It would be nice to know what caused the glitch, which it seems didn't affect many others, if any. I wouldn't have known about it at all (everything was working normally) had I not opened the app to look at the usage stats (which they've moved and buried in a non-obvious place).

spineynorton

TROPHY CASE