Structure of 16-bit grayscale image to be generated in C or LabView
I have a kind of basic (but still unresolved) problem. I'm building a program in LabView in which I gather a large amount of measurements into a n x m matrix, and I need to convert that matrix into an image to be processed/analyzed with ImageJ. Due to resolution and the kind of analysis I need, this has to be a 16-bit grayscale image.
Now, the problems I'm facing are the following: LabView does not have (on the basic package) any VI to transform data into 16-bit grayscale, only 8-bit, which kills my dynamic range. I've read around that the Vision and Image toolboxes of LabView might have more options in that sense, but for company-related reasons I cannot access these toolboxes (i.e. I have to make do with the Full Developer version only).
My reaction at the moment is to try and build on my own a VI to build a 16-bit grayscale image, whether by using standard LabView functions, entirely with C code, or mixtures of both. However, I haven't found any clear-enough information on the web regarding how a 16-bit grayscale is structured, what data is needed, etc.
So, my question is twofold: does anyone have a better way of creating this 16-bit grayscale image (some LabView VI I've skipped, external software I can invoke, etc.)? If not, does anyone have detailed information or code useful to generating such an image from scratch?
Any help will be really useful! Thanks!
Install IMAQ module (different than the vision toolbox), it is free and has basic image management capabilities. I use it for creating 16 bit grayscale images.
Find IMAQ driver here (4.6.4 as of June 2012).
- Is this declaration UB?
- Calling an external C function (in a shared lib) from Perl with Inline/C does not work
- Eclipse C/C++ how to find variable belongs to which struct quickly
- Is this truly best way to delete last element in C?
- Why do we need address virtualization in an operating system?
- Can a real floating-point type alias a complex floating-point type in C?
- Shadowing an iterator inside a for loop has undefined (?) behaviour in C
- Can a C program execute successfully if main() is defined as a macro?
- Ambiguity in scope of for loop declaration versus body
- Understanding the difference in timing of two functions that increment each element of an integer array
- Why MSVC generates warning C4127 when constant is used in "while" - C
- Executing a user-space function from the kernel space
- Why must the variable used to hold getchar's return value be declared as int?
- mpirun -np 4 ./a.out doesn't use all my cores (ubuntu 24.04LTS)
- Sleep for N seconds and wait for keypress
- Dereference twice in gdb
- Is it safe to cast a struct pointer to a different struct pointer having a prefix of elements?
- Can a C compiler legally reject a program if its call stack depth exceeds a fixed limit at compile time?
- return type defaults to 'int' [-Wimplicit-int]
- What is the scope of `fesetround()`?
- Which specific optimization flag causes libm functions to be treated as pure?
- How to render text in SDL2?
- Why would you use 'extern "C++"'?
- Strange Behavior Compiler Ignoring NULL Check Unless I Print Something in the if Statement
- Fast inverse square root using fixed point instead of floating point
- What is the const qualifier attached to in C: the memory area or the pointer?
- GCC options for strictest C code?
- How to do an explicit fall-through in C
- How do compilers treat CONST qualifier when the pointer points to a memory location obtained with malloc()?
- C: cmocka headers - how to unittest?