@korijn I'm glad you find our DICOM Standard Browser to be useful!
You (and others reading this post) may be interested to know that the JSON data the powers the browser is extracted using a set of open-sourced Python scripts:
197 karma · joined September 13, 2012
I'm also the CEO and Co-Founder of Innolitics (innolitics.com).
Our mission is to accelerate progress in medical imaging by sharing knowledge, creating tools, and providing quality services to our clients, with the ultimate purpose of improving patient health. We do so while providing meaningful, flexible, and financially rewarding careers to our team.
I write articles here: innolitics.com/articles
You may contact me at "jdgiese@innolitics.com"
You (and others reading this post) may be interested to know that the JSON data the powers the browser is extracted using a set of open-sourced Python scripts:
Absolutely; I think the regulatory documentation management needs for software and hardware are different. E.g., several of our clients (including one we used our RDM tool in conjunction with) use https://www.greenlight.guru. They seem to like it for hardware work, but we have had a tough time using it for software work.
One big problem we see with our RDM tool is that it isn't very usable for non-developers. Thus, it makes sense primarily for smaller early stage teams where they don't have and regulatory specialists.
(BTW if you are shooting for IEC 62304 compliance, you may want to checkout https://github.com/innolitics/rdm ; it isn't as polished as we would like, but we have a lot of interest in this tool)
But I was surprised by your comments about truth:
> There is no such thing as an absolute truth, after all. And pretending there is, and it's even attainable, is intellectually dishonest.
Could you expand on what you mean by "an absolute truth?"
I may be misunderstanding you, but I suspect you mean that we can never know anything with absolute certainty. For example, it may _seem_ that I typing on a keyboard, but in actual fact, I am dreaming.
In this example, there _is_ an absolute truth. I am typing on my keyboard, or I am not. But that truth is not knowable without any doubt.
If we use "truth" as high as knowing without any possible doubt, then nothing is "true." Thus, the word true is useless during everyday communication. For this reason I don't think it is appropriate to qualify everything we say with, "we don't know with absolute certainty this is true, but here is my best guess." Rather, we just say it is true.
It is hard for me to understand your point of view on this.
What is the difference between saying "modern people have too much free time" and "modern people live too long?"
> What would I do with an extra 30 minutes? Probably check Hacker News or Facebook more than I already do.
Some things you can do in those extra 30 minutes:
- Read a book
- Call an old friend
- Paint, write, or create something
- Code on your hobby project
If you think checking hacker news or Facebook is a waste of time, then don't, and find something more worthwhile to do instead.
Most larger buildings have a washer and dryer in the basement of the building.
Many people send their laundry out to have it washed and folded by someone else.
1. planning meals (may be minimal if you can ad-hoc quickly)
2. walking/driving to the grocery store
3. cooking
4. cleaning
It can easily be more expensive for an individual person (or even a couple) to cook than it is to eat out. (I think this makes intuitive sense too, since there are economies of scale and efficiencies with how restaurants are run.) If you love cooking, then you are doing it for fun---thats great! But I think for people who don't like cooking, it can be rational to eat out for most meals.
Many people are not paid at an hourly rate, so this analysis may not make sense for them.
(Also, where I live, there are plenty of healthy and cheap places to eat out at.)
What is inconvenient about not flushing the toilet if you only urinate? I may have a weak nose, but I have never smelled anything. If you are skeptical that this is the case, I would try for a couple days and see what you think.
I think the amount of water saved is higher than you expect. I work from home and drink a lot of coffee, so maybe my usage is higher than yours.
According to https://www.home-water-works.org/indoor-use/toilets:
> Toilet flushing is the single highest use of water in the average home, so it also presents a prime opportunity for water conservation. With the average person flushing five times a day, toilets make up about 31% of overall household water consumption.
- I try to avoid buying new things for as long as possible. When I can, I repair what I own or buy used. Living in a small apartment provides some natural incentives to avoid buying too much stuff.
- I avoid eating meat, and when I do, try to eat Chicken or fish.
- I try to take short showers and don't flush the toilet if I only urinate (it took my wife a while to get used to this, but she came around after a bit).
- I avoid using paper towels and reuse aluminum foil and bags as often as possible (often, you can wipe off the aluminum foil and use it a second or third time).
Some of these may not make much of a difference.
I have not spent too much time thinking about this, so my reasoning may be faulty, but I will share it anyway:
I am more worried about deforestation and the rainforests and poaching than climate change.
I want to keep a healthy planet so that conscious beings, and especially humans, can continue enjoying it. Thus, there is a balance between enjoying life (e.g., traveling) and reducing emissions. It seems, as is often the case with difficult ethical questions, that finding balance is key.
Innolitics is a ten-person fully-remote services company specializing in medical imaging software.
Our mission is to accelerate progress in medical imaging by sharing knowledge, creating tools, and providing quality services to our clients with the ultimate purpose of improving patient health. We do so while providing meaningful, flexible, and financially rewarding careers to our team.
We have two open positions:
* Junior Developer: https://innolitics.com/join/junior-developer-2020 ($70k - $80k)
* Developer: https://innolitics.com/join/developer-2020 ($80k - $100k)
See the job postings and our company handbook (https://innolitics.com/about/handbook/) for more details.
Compare:
{ a; b && c; } ≫ log.txt
from subprocess import check_call, CalledProcessError
f = open("log.txt", "a+")
try:
check_call(["a"], stdout=f)
except CalledProcessError as e:
pass
try:
check_call(["b"], stdout=f)
check_call(["c"], stdout=f)
except CalledProcessError as e:
exit(e.returncode)
exit(0)
> To accelerate progress in medical imaging by sharing knowledge, creating tools, and providing quality services to our clients, with the ultimate purpose of improving patient health. We do so while providing meaningful, flexible, and financially rewarding careers to our team.
So it is nice to hear that, to some degree, we are accomplishing the "creating tools" part of this.
Please do let us know if you have ideas for improvements.
We just added a new feature yesterday---it is a new tab that allows you to analyze a DICOM file within the browser, see the values it contains, and easily cross check the tags with the standard. Any feedback would be welcome.
Here is a screenshot of the DICOM file analysis feature in action:
https://innolitics.com/img/dicom-file-upload.png
Edit: make it clear the files are not uploaded to any server, but stay within the browser
The most authoritative source on DICOM is the free standard:
https://www.dicomstandard.org/current/
It is not particularly easy to read and thus not a great starting place.
The DICOM forum is a good place to ask questions:
https://groups.google.com/forum/#!forum/comp.protocols.dicom
David Clunie, a very nice guy and the editor of the DICOM standard, is active on this forum. He also has is own website that has many other links:
If you are interested in parsing or generating DICOM files, our DICOM standard browser is a great resource:
https://dicom.innolitics.com/ciods
I also wrote a very brief article about DICOM, which was meant to be the first in a series of articles, but alas I have been to busy to continue them:
https://innolitics.com/articles/dicom-i-facilitating-interop...
Oh, and here is a pretty good blog about DICOM:
http://dicomiseasy.blogspot.com
Checkout his "DICOM Tutorial" in the sidebar.
If you have any particular questions about DICOM, message me and I would be happy to try and answer them.
Over-prescribing antibiotics is bad because (1) some children have serious allergic reactions to them (and sometimes these develop over time), (2) they contribute to the evolution of antibiotic resistance.
https://www.youtube.com/watch?v=XD0FEcK9smE
The speaker (I believe a professor) makes some very compelling connections between the Iliad and gang culture. It gave me a new way (but certainly not definitive) way think about the Iliad. If I recall, he may also discuss PTSD towards the end.
I reconcile the concept that code is a debt with your statement in the following way:
The feature produced by a piece of code can be an asset, but the code itself is a debt.
Thus, for a new feature to be valuable, you want the value added of the feature (or asset) to out-weight the cost of the code (or debt).
As a general rule, the complexity that comes along with a piece of code grows as the code-base and feature set grows, thus, for a young codebase, the value of a feature more easily out-weights the cost of the code.
I love living in a place with so many people, great museums, and great restaurants. It’s very walkable and I love the subways. I meet many interesting people at coffee shops and in the park.
The taxes are a high but overall it is cheaper than I expected.
I found the response to be quite reasonable, and certainly not worrying.
Why would it be a good idea to ignore people that disagree with you? It seems like it would be better to provide rational counter arguments, in the hopes of starting a useful discussion.
I have used Redux on a few projects, largely due to the hype (I.e., good recommendations from others in the community) surrounding it. Without intending to I ran into several discussions on SO and Github where Dan explained why people may not need redux. I think this is a very nice thing, and I think it is unfair to blame Dan or other developers for not reining in the hype more.
I do agree that the title of the article is a bit alarmist and perhaps counter productive.
Perhaps we are using the word careless differently, but I don't see how using heuristics like this implies carelessness on behalf of the employer. If anything, it seems to indicate that the employer is making a well-reasoned choice to balance economic constraints with company values.
I run a small software consulting firm and have now hired three people (not too many). I believe that attention to detail and pride in how you present yourself, either via your resume or your code quality, is essential. For this reason, I think applicants should spell-check their resume (or use Grammarly).
In fact, we even mention this in our company values page:
> We value correct grammar and a strong grasp of the English language.
> We write with a clear and professional tone in our external communication.
> We try not to send vague or confusing emails.
> We invest in improving our writing, presentation, and conversational skills.
Anyway, I certainly don't mean to discourage your pursuit of becoming an MD--I am just very curious to know your reasoning.
http://innolitics.com/10x/advanced-bash-exercises/
Also has some other useful BASH links and comments. Here is a quote:
> BASH is the most widely-used and widely-supported shell for Linux. There are other shells that are better than BASH in various ways, but we feel that none of these other shells are better enough to warrant replacing BASH as the de-facto standard when writing shell scripts. BASH is installed by default on almost all Unix-based operating systems, and the majority of the world’s shell scripts are written in BASH. For this reason, we suggest that all of our developers learn BASH.
> BASH scripts are a domain-specific programming language that is well-suited to managing processes and files. That being said, the large number of special characters appropriated for process management, its text expansions, and its unusual syntax make BASH poorly-suited for general purpose programming. Accordingly, we think that BASH should only be used for scripts that are predominantly concerned with processes and files.