I am trying to extract encoded information like this from the VVC compression-log. Is there any setting, config in EncodeApp source for writing output values to file, I am using VTM Encoder Version 8.2. Thanks
lick here to view
Your question is pretty unrelated to the topic of video compression.
But anyway... What you may do is to read the console output and parse it. To do so, you can first write it into a text file by adding > log.txt at the end of your command line. Then, parse the text file and write it to a CSV file.
You could save the screen context as *.txt ( for instance:EncoderApp.exe -c xxx.cfg>Enc.txt, and convert Enc.txt to Enc.csv( Implemented in Python )
Related
I have made a few corrections to location names in a GeoLite2 CSV file.
My site only retrieves locations from the MMDB file, so how can I compile back the changed CSV file into the MMDB binary again.
I searched everywhere for a solution but can't find it.
Thanks for any tip.
Carlos
Currently there are only 2 open source MMDB file writers:
MaxMind::DB::Writer (Perl language)
Go MaxMind DB Writer (Go language)
The second one unfortunately has only a subset of the features available for the Perl one, but it should be enough for writing a program that creates the MMDB file reading line by line the CSV one and creating the mmdbtype instances.
You can check out our mmdbctl utility tool.
To convert a CSV file to an MMDB file use the import command:
$ mmdbctl import --in data.csv --out data.mmdb
Instructions, features, and documentation are available here: github.com/ipinfo/mmdbctl.
Right now it only supports string data types, and not nested data types. See this issue for more information.
I am working with open source package written in python.
Its output is a file with .sww format.
I am unable to find a software which can read this.
Please kindly reply if you know.
Thank you
this is picture of the file icon
It's time to answer my own question.
SWW file format is a NetCDF format for storing model output with mesh information f(t,x,y).
One such use of SWW file extension is
In ANUGA, a hydrodynamic modelling. It's used for storing the model output and therefore pertains to a set of points and a set of times at which a model is evaluated.
The contents of an SWW file may be viewed using the anuga viewer anuga_viewer, which creates an on-screen visualisation.
I want to uncompress a gz file (e.g. "MyFile.gz") and saving its content in a specified path using zlib in C++.
In other words, if the path is "C:\StoredData\", I would like to write a C++ function that creates the file "C:\StoredData\MyFile"
How can I write it?
I do not understand what is the problem here.
Once the data is uncompressed, you can write it anywhere you want using the File Stream.
If you are facing any issues, you can edit your post.
Sorry to post as answer, as i can't add comments.
Read the documentation in zlib.h. The gz* functions will do what you want on the uncompression side. Then you just write the uncompressed data wherever you like.
I need to parse a log file that consist in many screenshot of real-time OS stdout.
In particular, every section of my log_file.txt is a text version of what appear on screen. In this machine there's not monitor, so the stdout is written on a downloadable log_file.txt.
The aim would be to create a .csv of this file for data mining purpose but I'm still wondering what could be the best method to compute this file.
I would the first csv file line with the description (string) of the value and from the second line I would the respective values (int).
I was thinking about a parser generator (JavaCC, ANTLR, etc..) but before starting with them I would get some opinions.
Thank you.
P.S.
I put a short version of my log at the following link: pastebin.com/r9t3PEgb
I want to convert all the .odt .doc .xls .pdf files to .txt files.
I want to convert these files to text files using a shell script or a perl script
There's a program for odt files and alikes:
odt2txt - avaliable in repos.
$ unoconv --format=txt document1.odt
Should produce document1.txt.
OpenOffice has a built-in document converter capable of handling a bunch of formats- take a look at unoconv: http://dag.wieers.com/home-made/unoconv/
That being said, I have had some troubles getting that to work in the past- If you're having trouble, take a look at similar programs for AbiWord (another open source word processor).
For word documents, you can try antiword, at least on linux. It's a command line utility that takes a word document as an argument, and spits out the text from that document (as best as it can figure) to Standard Output. Maybe you can specify an ouput file too. I can't remember the details of how it works. I haven't used it in a while. Not sure if it can handle OO documents.
It's certainly possible to do this, though there is something strange and impenetrable about the OO project and its documentation that makes things like this hard to research and follow. However, OO has the capability to convert all of those types, not just the OO native ones, and it can do it via two different forms of automatic control.
These are the two general approaches.
You can start OO and tell it to execute a macro which does this job for you for a given file. You then just have to write the macro and a script to loop over your files. The syntax is something like
$ oowriter -headless filename macro://dir/Standard.Module1.sMySub
The other thing OO has is a network API. This is based on something called UNO.
$ oowriter -accept=accept-string
Notifies the OpenOffice.org software that upon the creation of
"UNO Acceptor Threads", a "UNO Accept String" will be used.
You will need some sort of client library. I think they have one for Python at least. Using this technology a Python program or some other scripting language with an OO client library could drive the program and convert all the files. Since OO reads MSO, it should be able to do all of them.
Open the file in LibreOffice. Click on "File", "Save-as" scroll down to find the text option. Click that and it will be saved as a text file.
FYI, I had an *.ODT file that was 339.2 KB in size. When I save-as text the size of the file shrunk to ONLY 5.0 KB. Another reason for saving your files as text files.
For the Microsoft formats, look into the wvWare tools.
Open .ods file normally in libre office
Highlight text to be converted
Open a terminal
Run vi
Press "i" to get insert mode
Press ctrl-shift-v
Done!
Need some formatting?
Save the file as
Get out of vi
Run:
$cat | column >filename2
This worked in opensuse running KDE
Substitute "kwrite" for "vi", if you want