I actually just opened an issue <https://github.com/timholy/Images.jl/issues/267#issuecomment-81037699>over at Images.jl, to further modularize it, so that all the actual import functions are not part of it and live in their own package. This is nice, if you for example just need an jpg importer, or nrrd importer without the rest. This fits in my greater scheme of having a unified IO infrastructure, which is why I created JuliaIO <https://github.com/JuliaIO>. See the proposed interface in FileIO <https://github.com/JuliaIO/FileIO.jl>. I personally think this will be awesome! If anyone finds any short comings in this approach, please open issues =) If you have any IO package, feel free to join JuliaIO and contribute to it! It's not very sophisticated yet, so I'd appreciate any help in sketching this further out.
Am Samstag, 14. März 2015 13:41:04 UTC+1 schrieb Christian Dengler: > > Hello, > > I'm trying to save my data as .vtk files, and ran into a problem with the > "print" and "write" function. > > Resumee of what would solve my problems: > - Using print(filestream, data), but omitting the square brackets, and > - using print(filestream, vector), and actually writes the vector, one > element per line > > Does anyone know how this is done? > > Another way of creating .vtk files using binary data, using the write > function, didn't lead to any success, but i cant really say whats wrong, > because the files are unreadable. Could it be, that write also somehow > includes brackets? > > > For those who want to see my problem in code, i attached a script, > creating and saving a simple veocity field as .vtk (ASCII) file. > After manually deleting the brackets, atleast the velocity can be imported > into paraview. > In order to create the binary .vtk file (thats not working at all), i used > to replace "ASCII" by "BINARY", and "print" in line 22 and 41 by "write". > > Greetings, > Christian >
