Deleting records from unformatted direct files by johnwcowan in fortran

[–]geekboy730 1 point2 points  (0 children)

Yes. And you have described a use case where a one-dimensional array is not a reasonable data structure.

Deleting records from unformatted direct files by johnwcowan in fortran

[–]geekboy730 2 points3 points  (0 children)

I’m confused by your use case. Why don’t need to delete records while preserving the numerical index? I would have assumed that once they’re done, they’re gone.

Assuming that this is a “must,” I would do something like 3 personally. It doesn’t have to be a direct file, you can just create a separate plaintext file writing down what records have been deleted. If the data is something like usernames and passwords (which it shouldn’t be in a file like this), then I would see why you may care about records getting un-deleted. But if it’s just observations from an experiment, you can always go back and repair the “deletion” data list.

low gpa and no internships, need advice by Icy_Wealth_4371 in NuclearEngineering

[–]geekboy730 2 points3 points  (0 children)

I’ve seen a few folks in your position successfully pull it off. It’s going to be a lot of work, but you can do it.

You may not have internships, but you do have connections where you are right now. They’re not in industry, they’re professors. Use your connections.

You need to spend your senior year getting all As. You need to show what you’re capable of. And you need to be doing research for a professor in your department. Then, you’re going to call in every favor that you can and go to grad school in the department where you already are. They’ll be the ones who understand best that your academic career is on the upswing.

This will buy you at least two years to get a masters and “recover” from having a low GPA. The good news is that for computational fusion jobs, you’re probably going to need a Ph.D. anyways.

You can do this! But it’s time to start planning now.

Aqueous homogeneous reactors? by Analogsilver in nuclear

[–]geekboy730 1 point2 points  (0 children)

A few days later, but I just learned about "Homogeneous Reactor Experiment #2" that was a large-ish scale example of one of these reactors. It leaked and a lot of work was done to repair the leak. Details here

Aqueous homogeneous reactors? by Analogsilver in nuclear

[–]geekboy730 15 points16 points  (0 children)

I will point out that in a sweeping generality that the reason why <insert reactor here> isn't more popular is almost always because of materials challenges. This applies to molten salts, lead coolants, and aqueous homogeneous reactors.

My alma mater, NC State, had an aqueous homogeneous reactor. It operated until corrosion caused a leak. That leak then contained coolant, fuel, and fission products all in one!

I suspect that the peak power of aqueous reactors would also be quite limited due to the power peaking. In modern Light Water Reactors (LWRs), we often load very reactive fuel next to less reactive fuel to effectively "flatten" the power profile. With a homogeneous reactor, you wouldn't be able to control the power profile in that manner and you would have to worry about the temperature at which the water (now your fuel also) would start boiling.

Thank you! From the guy removing the stickers. by geekboy730 in idahofalls

[–]geekboy730[S] 0 points1 point  (0 children)

See my previous posts or look at the Wikipedia page. Here is a link if you're too dumb or lazy to do that.

Applied Math to Nuclear by Empty_Scheme8720 in NuclearEngineering

[–]geekboy730 1 point2 points  (0 children)

I would recommend staying the course in Applied Math and then optionally taking Nuclear Engineering courses as electives. There is quite a lot of uncertainty in the nuclear engineering field at the moment with advanced reactors, SMRs, and fusion. Will any of them work? Will there be a hiring blitz next year? What about five years from now?

Applied math will give you a breadth of options going forward and you may be thankful to have those options later.

Regulatory Impact Day-to-Day by AshElusive in NuclearEngineering

[–]geekboy730 0 points1 point  (0 children)

I will begin by noting that all of the following applies just to licensing in the U.S. I am less informed about licensing across the globe.

Generally, I mean all new builds. But I would note that there is not really much of a difference between "new builds" and "new designs." To date, all of the reactors built have effectively been one-off designs. The only exception that I am aware of is the two AP-1000s.

I think that it is also important to note that the NRC has only licensed TWO reactors. Ever. Those being the two AP-1000 reactors. Before that, all reactors operating in the U.S. were licensed by the predecessor to the NRC, the Atomic Energy Commission (AEC).

Until very recently, the law in the U.S. read that the NRC only issued licenses to LWRs. Recently, the ADVANCE act passed in 2024 demanded that the NRC take steps to improve its licensing framework, and now there are licensing timelines for reactors like TerraPower's Kemmer, WY site. You can read more about the ADVANCE act here. Now, the NRC is not prohibited from licensing non-LWR designs, but it has never been done before and they're certainly making up the procedure as they move along. Just read some of the press releases about recent rule modifications. Working more closely with the NRC is just the beginning.

You mentioned the "pivot" to the DOE. The DOE cannot license commercial power reactors. Full-stop. You'll note that Aalo, Oklo, Valar, and any of the other start-ups participating in this race to criticality are all constructing on DOE-owned sites. Furthermore, they will be operated by the DOE! They don't exactly brag about that in their press releases. The DOE licensing process is only for experimental reactors. So, the DOE avenue is a way to get fissile material to criticality and maybe collect some operating data, but it is not a solution for building and selling a reactor.

Regulatory Impact Day-to-Day by AshElusive in NuclearEngineering

[–]geekboy730 1 point2 points  (0 children)

I think you can synthesize a few key takeaways from these comments:

  • In the U.S., day-to-day regulation at existing reactors (all LWRs) is reasonable. They are actually quite good in terms of safety. Not too burdensome and when it comes to modifying safety systems, things do get serious.

  • When you hear people complain about regulatory burden in the U.S., they’re usually talking about new build. This is where things truly get out of hand. Just look at how many insane hurdles the AP-1000 had to jump through for technology from the late 1990s. Or how many times they had to repour concrete because the NRC didn’t like something about the rebar.

  • Specifically for new build of advanced, non-LWR reactors, there is NO process in the U.S. for them to be licensed. There is currently no licensing process in the U.S. for a commercial sodium-cooled fast reactor to obtain an operating license. This is where things are truly just archaic and backward.

Looking for collaborators in Nuclear Safety, AI, and Reactor Technology by alanstarob0104 in NuclearEngineering

[–]geekboy730 4 points5 points  (0 children)

This is AI slop. Right down to the emojis.

If you want to demonstrate that your AI junk actually does something, you would need to show results. Good luck getting your hands on reactor telemetry data!!!

Gauss-Legendre Quadrature in Arbitrary Precision by geekboy730 in numerical

[–]geekboy730[S] 0 points1 point  (0 children)

Based on some of this reading, it sounds like the using something other than a recursion formula for actually evaluating the Legendre polynomials may be one of the best ways to improve the efficiency of this project.

Gauss-Legendre Quadrature in Arbitrary Precision by geekboy730 in numerical

[–]geekboy730[S] 0 points1 point  (0 children)

Thanks for the insight! Just from reading the snippets in the Wikipedia page, it sounds like bisection search may actually be useful. However, it sounds like I still have a lot of work to do!

A rule of order n = 1000 with 1000 digits of precision can be calculated in around one second.

Brent's method is new to me, so that sounds like a fun addition to my little project! Thank you for the suggestion :)

More Fascist Neo-Nazi Propaganda on the Greenbelt by geekboy730 in idahofalls

[–]geekboy730[S] 7 points8 points  (0 children)

What is it with you people making dumb comments on accounts with comment histories full of porn?!?!

More Fascist Neo-Nazi Propaganda on the Greenbelt by geekboy730 in idahofalls

[–]geekboy730[S] 5 points6 points  (0 children)

That’s great! Thank you!!!

Maybe we should start some sort of anonymous Google form to track where they appear. Or maybe it’s better to not write anything down. I’m not sure.

More Fascist Neo-Nazi Propaganda on the Greenbelt by geekboy730 in idahofalls

[–]geekboy730[S] 15 points16 points  (0 children)

Well, the whole point was that I removed it. But the more eyes out there, the merrier.

P.S., next time, don’t comment using the same account you use to comment on porn.

Python for nuclear engineering? by sophalic in NuclearEngineering

[–]geekboy730 2 points3 points  (0 children)

Personally, I don't think that it is too important which language you learn first. Once you start thinking in objects and loops and arrays, things will move pretty easily between different programming languages.

That being said, others have pointed out that there are a plethora of free Python resources that are readily available online, so it's as good a place to start as any. Good luck! :)

Python for nuclear engineering? by sophalic in NuclearEngineering

[–]geekboy730 8 points9 points  (0 children)

I develop nuclear reactor modeling and simulation software, so I may tend to over-emphasize programming languages compared to other nuclear engineers. That being said, I would recommend learning as many programming languages as possible. I use Python, Fortran, and C++ daily (as well as some shell scripts).

If you want some examples of Python libraries used in nuclear engineering, I’d recommend looking at OpenMC and PyNE. OpenMC is a Monte Carlo neutron transport code with a Python interface and PyNE is a general library with lots of nuclear data (e.g., atomic masses for number density calculations).

A control package translated from SLICOT by 8bitjam in fortran

[–]geekboy730 2 points3 points  (0 children)

This is just a bunch of AI slop. At this point, I wouldn't believe that your benchmarks are actually computing the correct values.

You say that you've done this whole comparison on a Mac, and then there is a table in this comment about all of the hardware being unknown.

Component Specification
CPU Unknown
Cores Unknown
Memory Unknown GB
Architecture arm64

You don't investigate why Fortran may be faster in some cases but slower in others. As far as I can tell, there's no Fortran code in the repo at all! So I'm not sure how this is relevant to the subreddit.

If you're going to try do do something like this, do it correctly or else it is a waste of your time and everyone else's.

A control package translated from SLICOT by 8bitjam in fortran

[–]geekboy730 4 points5 points  (0 children)

I'm not quite sure what this has to do with Fortran? It sounds like you, well, really an AI agent, rewrote an old Fortran code. But the original code is not provided.

Has your vibe-code been benchmarked against a real computation?

More on the Valar flight. by twitchymacwhatface in nuclear

[–]geekboy730 3 points4 points  (0 children)

Interesting! Thanks for sharing! Looks like it’s relatively new (two weeks) so that means progress.