I second OBS. It works great for capturing windows and screens. The only issue I had with it is that Windows Media Player won't play the "Advanced Video Codec" that it records with, so I had to run it through Handbrake.
On the flip side, I found that OBS brought my -- admittedly older -- MPB to its knees such that the app I was trying to show wouldn't perform. Huge lengths of video were frozen. Same on an older first-gen i7 Windows machine. I never did figure it out.
This is probably a configuration issue, although OBS has more issues OS X for a variety of reasons. I've ran OBS on my 10 year old PC while coding without much issue.
VLC is not optimized to prioritize video quality at all last time I saw or used it. Additionally, it felt clunky and seemed to perform worse than MPC-HC.
I wonder if it's just the profile that WMP has problems with. I'd be interested in comparing the `mediainfo` output of both a Handbrake and a OBS encoded video - I suspect Handbrake is still extremely conservative with what it outputs (at the expense of a bit of quality)
If you look carefully, everything for the whole video is replicated 9 times. These simulations typically use periodic boundary conditions: if something goes out the left side, it is put in at the right side, and so forth. This significantly decreases boundary effects that would arise from putting interfaces into the simulation. Only one of the 9 cells is really being simulated, but they replicate it once in each direction for visualization so you can see what is happening through the boundary conditions.
Gotcha! I've done some basic 2D simulations of blood vessels using COMSOL, but those only took minutes to run. This must have required some beefy hardware or some really good code. It's really quite amazing how well simulations can match reality.
> But I feel like I'm looking at a laundry list of mostly minor, tiny issues, that are a "solved problem" in the form of existing warnings.
I'm not aware of warnings for uninitialized variables in constructors. Can you clue me in how to get these on in Visual Studio? I'm using a third party tool that can detect uninitialized scalars only and would love to have the extra scanning.
Sadly Visual Studio's compiler has no warning I'm aware of. Using /sdl will forcibly initialize all your members however - I guess Microsoft's approach to the problem is that fixing it for you is better than giving you ignore-able warnings.
There are third party tools - such as cppcheck - which should catch uninitialized members however.
I generally also compile with clang, which catches a lot of additional stuff for me.
And here's a random John Carmack link noting some of the static analysis tools out there:
I've been playing around with clang's Address Sanitizer all day as well, catching buffer overflows and underflows left and right in a janky old codebase I was suddenly thrust into recently...
We are (slowly...) doing the same thing across our codebase. The tool we use -- PVS-Studio -- just introduced checking for uninit'd scalars so we are grinding those down and doing eyeball checks in the ctors, but I was hoping for a more reliable method for the latter portion.
At the very least that would help remove random behavior at the cost of speed (if I understand correctly). I'll have to sleep on /SDL and do some perf testing come Monday. I had really wanted to use /analyze (https://msdn.microsoft.com/en-us/library/d3bbz7tz%28v=VS.100...) but it crashes! D:
Unfortunately, I'm rooted in Windows SDK and I don't think clang supports that. The Microsoft Application Verifier has some run-time memory checks, so I'm not totally unarmed.
I looked at PC-lint doesn't have complete support for C++11 yet and I'm worried about the rate of false positives. I had not heard of cppcheck, so I'll have to give that go since it looks free.
I'm not who you are replying to, but I am a developer at Merge who is excited to try out your toolkits! I think there are a ton of opportunities for medical image analysis in the PACS world. I really hope that IBM will challenge us with the task of integrating Watson-technology into the PACS workflow. We've got some really smart employees here and I am hopeful this represents a huge opportunity for us.
(Secretly I can't help but think the smart business decision is to "black box" the image analysis as much as possible, but I can't help but being giddy about it even so!)
