The (corrected) drag coefficient was close to the published one (note that this model has a smooth under body surface, and there is no cooling drag either).
[Not to hijack my own thread but… I had seen Dolfyn, and to a degree it, or actually what surround it suffers from the same think that Calculix does: we don’t see a lot of examples, and how would we, as mere mortals use it?
In the case of Calculix, I would have never guessed how good it is?
Calculix’s website is better than “engineering UI ghetto” we don’t quite see what it can really do. I don’t think on the main page it even mentions a heat-coupled FEM solve, which it can do.
But until it was adapted into a convenient pre-processing solution, Calculix went unnoticed by most, and wrongly under-opinioned by myself.
Also noting that Coefficients of drag can’t be calculated in OpenFoam, and are traditionally done in Paraview. I think we have to do an integration over the surface normal, but my solves had issues with a missing parameter to form one type of normal.
Automatic drag coefficients would be handy, during the solve, as would be lifting or hopefully squating forces.
Ironically, doing a linear by layer mesh without a growth rate is more sic “unbiased,” but as I find at 50GB memory use @ 10mm hexahedrons, is not very memory effecient. I have had a few SnappyHexMeshes fail during OpenFoam solve. ]
Are you just guessing, or do you have LTSC experience?
If the latter, please share a few details with us.
I’m not an IT person - just an average user placing high priority on privacy and security.
Before using LTSC, I worked with Windows 10 Pro for about a year, and I can only say: YES, there ARE a differences.
An example: On every operating system, I disabled Windows Telemetry in the registry. Due to automatic updates on Windows 10 Pro (which can’t be turned off), this setting was occasionally reset, along with other settings related to diagnostic and location “services.”
On LTSC, I never noticed anything like that.
Furthermore, there are no automatic updates, so I can always decide for myself what I want to install and what not.
And (most importantly): LTSC receives ONLY SECURITY UPDATES. There are neither feature- nor app-updates.
If you place a high priority on privacy and security you wouldn’t be using Windows
I will be honest though I’ve not used LTSC before. However I do have a good amount of Windows experience in an enterprise environment.
I wouldn’t trust any settings you see in the Windows desktop UI to be gospel on what is or isn’t being sent to Microsoft from your device. Try proxying traffic coming from pre-installed windows apps on the host & also the network traffic coming from the host. There is an incredible amount of telemetry and data that Windows phones home with & I would bet that LTSC does the same thing, but I do not have any specific examples of how LTSC behaves. Maybe I’ll investigate that one day.
Microsoft is not in the business of allowing their users to be anonymous. It was easier to maintain a level of privacy on windows in the past but it gets more difficult each update. Abandon ship.
I would be very much interested in your results! Please dont hesitate to publish them here. As stated before, I use LTSC 2019 (Build 1809).
Meanwhile - as a non-pro in terms of IT - I’m limited to standard web searches. Obviously there here have been rigorous, legally definitive studies by the German Federal Office for Information Security (BSI) under the SiSyPHuS Win10 project, alongside empirical findings from enterprise security firms. [1, 2, 3]
1. Key Findings: What the Intercepted Traffic Contains
When LTSC 2019 is heavily restricted via Group Policy Object (GPO) (Telemetry Level 0 / “Security”) and traffic is proxied, analysis reveals specific behavioral patterns: [1, 2]
Telemetry Suppression is Successful but Incomplete: At Telemetry Level 0, the central telemetry component (DiagTrack / diagtrack.dll) can be almost completely muted. Studies by BSI and independent labs show that a fully hardened LTSC 2019 instance can sit idle for days without transmitting user behavioral telemetry. [1, 2, 4]
The “Zero-Traffic” Myth: Even at Level 0, residual structural traffic persists. If not explicitly disabled via deep GPOs or blocked at the proxy, the host will attempt to bypass local restrictions to hit specific Microsoft endpoints:
Certificate Trust Lists (CTL): The host frequently hits ctldl.windowsupdate.com to update root certificates.
NCSI (Network Connectivity Status Indicator): Hidden HTTP/DNS requests to ://msftconnecttest.com to check if the machine has live internet access.
KMS / Activation Validation: Cryptographic verification requests to Microsoft licensing endpoints. [1, 2, 3, 4, 5]
As stated before, LTSC is a quite minimalistic OS - (nearly) without any pre-installed apps.
For example, here is a screenshot of "Windows-accessories on my start menu:
Great comment! I appreciate the detail and thanks for citing some sources. I’m intrigued now and will look into this research topic.
Currently I only have Linux computers (hence my effort to get rhino working with wine) however I’d always choose a Mac over windows these days and I’m considering getting one for creative programs. The m chips are impressive and I appreciate the hardware security features Mac’s have been implementing over the years. Also their approach to application permissions on a per directory basis (among other controls), and all those “do you want to allow access” pop ups i actually like and think are a good feature from a security/privacy perspective. I haven’t seen any other OS do something like that yet.
Also the start menu accessories is usually only a partial picture of what’s on the box. But I am curious now what windows services are actually running on LTSC. For example - if LTSC is designed to be a stable version of windows with the goal of maximum uptime in a windows enterprise environment, i imagine it will have all the bells and whistles required for Active Directory integration and possible Azure syncing as well. I will investigate and update you at some point.
Thanks a lot for the detailed explanations and the OS recommendation!
I envy anyone who is able to set up a stable working environment running Linux.
Azure is not natively included as part of Windows Enterprise LTSC 2019 or any later LTSC version. LTSC is designed as a stripped-down, stable operating system for specialized devices and does not include any cloud services by default.
It took me quite a bit of extra work to configure LTSC to my needs and I’m not entirely sure what exactly each setting is for. So there’s a fair amount of trial and error involved and I’ve been guided by various websites like this one: Windows 10 LTSC Post-Installation Guide
I very much agree to this!
Using portable Apps is quite a good alternative for Windows and I use them as much as possible.
When logged in as User (not Admin) I am frequently asked the “do you want to allow access” question.
Indeed, but this is not a great time to throw away a bunch of computers, and buy new ones–is it?
Admittedly, I do like stimulating the open hardware market, because it provides choice, but if someone put a Mac Studio down in front of me that had 256GB of RAM, it would make choices and virtue more complicated.
Inspired by our discussion, I rechecked my Telemetry settings and found that I simply had “disabled” Telemetry in the “Group Policy”. According to this source, in LTSC (and Enterprise) - unlike other Windows versions - you can set Telemetry to Level 0, which (nearly) totally mutes the central telemetry component (DiagTrack / diagtrack.dll). Interestingly, to access the drop down for the different levels, you first have to activate Telemetry (Microfoft logics).
So again: YES, there IS a difference between LTSC and Pro.
What are your suspects for other Apps/components installed?
Any ideas how to check what else is “in the box”?
If one day you decide to do so, it would be interesting to also investige traffic after disabling some specific services.
Not a lot of examples no, but on the tutorial page there are a couple (based on Gmsh):
One can use any mesh (software, including Calculix), and if you like it, Paraview for postprocessing.
I am personally aware of a couple of codes (including three gas turbine combustion codes) which are originally based on Dolfyn. The structure already has been set up for ParMETIS. What is left to do is adapt the pressure solver. Then the road is set for LES as well. As for meshing, there are some plans too.
PS: I know that the site needs an urgent update after it was relocated. Time, time, my kingdom for time!