Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linked to libunserding.so.0 #5

Open
nkolster opened this issue Apr 20, 2013 · 5 comments
Open

Linked to libunserding.so.0 #5

nkolster opened this issue Apr 20, 2013 · 5 comments

Comments

@nkolster
Copy link

Hi!

Here is just a quick note, I installed twsgluum and unserding.

I was receiving this error:
um-quodmp --beef 9999 -o file
um-quodmp: error while loading shared libraries: libunserding.so.0: cannot open shared object file: No such file or directory

Then I made this symbolic link which fixed it:
sudo -u ln -s /usr/lib/libunserding.so.2 /usr/lib/libunserding.so.0
Probably just some typo or something somewhere, but otherwise it seems to have worked right out of the box. Thanks!

@hroptatyr
Copy link
Owner

Hm, I'm astonished that works. Actually, an unserding-0.4.x tarball build should install a libunserding.so.2, the 0.2.x and 0.3.x family provide libunserding.so.0.

The thing is that they're incompatible so unsermarkt/twsgluum is right in demanding the .so.2

@nkolster
Copy link
Author

Ok, i see.
Installed the unserding 0.3 tarball.
um-quomon seems to work ok, but um-quomon seems to give a bit weird output. Tried changing the console to UTF etc. But it didnt have any effect.

nk@i5:/rtrading/spreads$ cat file2
UTE+v0.2><ÞB@ÛôxQ@ó@b@ÛôxQ@ó@bÀ"ÛôxQJó@@klbÀ"ÛôxQJó@@klbÀGÛôxQJó@[AÀhÛôxQðò@bÀhÛôxQJó@ =A­ÛôxQõò@@ba­ÛôxQõò@@bÀ­ÛôxQ¸
.@@bÀ­ÛôxQ¸
.@@bÂÀGÝôxQðE @bÂÀGÝôxQðE @b@ZÝôxQe@°q
@zÝôxQe@°q
ÀÝôxQc@Pñ"ÁÀ£ÝôxQX
[BÀ£ÝôxQàô£ 0+6ÂÁÝôxQðE  AÂÁÝôxQà @bÂÁÝôxQà @bÁÝôxQb@ÀÆ-ÁÝôxQb@ÀÆ-ÁÝôxQc@Pñ"ÁÝôxQc@Pñ"AÁÝôxQÐÍ£ Pñ"ÁÝôxQßÁÝôxQßÁÀÁÝôxQX
=ÀÁÝôxQ@ÀÁÝôxQb@@BÀÁÝôxQ@ÀÁÝôxQa@°q
ÀÁÝôxQa@°q
ßÝôxQ¸àÝôxQ_@@bàÝôxQ_@ÀÆ-àÝôxQ`@àÝôxQ_@@bàÝôxQ_@ÀÆ-àÝôxQ wBÞôxQàô£ pmEBÞôxQXᣠBÞôxQXᣠÞôxQpÞôxQP@ÞôxQa@Pñ"@ÞôxQ_@ÀÆ-@ÞôxQa@Pñ"B@ÞôxQàô£ pmEB@ÞôxQàô£ pmE@ÞôxQß@ÞôxQ°Á@#ÞôxQX
B@#ÞôxQàô£ 0+6B@#ÞôxQàô£ pmEBEÞôxQàô£ 0+6Â@eÞôxQðE @bÂ@eÞôxQðE  AÂ@eÞôxQðE  A@EÞôxQb@Pñ"@eÞôxQc@°q
A@EÞôxQXᣠPñ"@eÞôxQ wÀjÞôxQ°kÞôxQc@Pñ"kÞôxQ°-@klkÞôxQ°-@klÞôxQc@0ö)ÀªÞôxQ w«ÞôxQa@Pñ"«ÞôxQa@°q
«ÞôxQa@°q
A«ÞôxQÐÍ£ Pñ"«ÞôxQ¸«ÞôxQ¸ÉÞôxQb@Pñ"ÉÞôxQe@Pñ"ÉÞôxQe@Pñ"BÉÞôxQàô£ pmEÉÞôxQßÉÞôxQ°@éÞôxQc@°q
@éÞôxQc@°q
A@éÞôxQXᣠPñ"B@éÞôxQàô£ Àû9B@éÞôxQXᣠ°q
B@éÞôxQXᣠ°q
B@éÞôxQàô£ Àû9ÚüÚü%ÿÿÿÝÿÿÿý
ÿÿÿÿÿÿÿüÿÿÿýÿÿÿûÿÿÿüÿÿÿúÿÿÿûÿÿÿùÿÿÿúÿÿÿøÿÿÿùÿÿÿ÷ÿÿÿøÿÿÿöÿÿÿ÷ÿÿÿõÿÿÿöÿÿÿôÿÿÿõÿÿÿóÿÿÿôÿÿÿòÿÿÿóÿÿÿñÿÿÿòÿÿÿðÿÿÿñÿÿÿïÿÿÿðÿÿÿîÿÿÿïÿÿÿíÿÿÿîÿÿÿêÿÿÿíÿÿÿéÿÿÿêÿÿÿÝÿÿÿú!$ÿÿÿý! ÿÿÿüÿÿÿþÿÿÿûÿÿÿÿÿÿÿéÿÿÿÿßüßüÿÿÿÿ@$"4)@%&"-130ÿÿÿÿ@$"4)@%&"-130ÿÿÿÿ@$"4)@%&"-130ÿÿÿÿ@$"4)@%&"-130ÿÿÿÿ@$"4)@%&"-130ÿÿÿÿ@$"4)@%&"-130nk@i5:
/rtrading/spreads$

@hroptatyr
Copy link
Owner

In what way is the output weird? Can you provide a screenshot?

@nkolster
Copy link
Author

Hi,

I didnt know the dumped files should be viewed with "ute print" so I thought I could view them with cat, like I tried above: http://i.imgur.com/A5J7HYG.png
Also with ute print I couldnt quite decipher it, but it was in ASCII again:).

I have to think a little bit about how to proceed. Gonna need some quote collection and what I have in java at the moment will need some serious modifications to be good for long-term use. I would hate to re-invent the wheel again and it seems you already have a working tool, just not so easily comprehensible:)

@hroptatyr
Copy link
Owner

Ah yea the good old ute ascii format:
The first column is the symbol name, the second is the tick timestamp.

The third column is the symbol index (in hex), for one and the same symbol this number should be the same.

The fourth column is the tick type in hex, as defined by the #defines in uterus' scommon.h (1 is bid, 2 is ask, 3 is trade, the rest is up to interpretation).

Then come either 2 more columns (in case of ticks) or 6 more columns in case of candles. Assuming you're looking at tick data this would be the quote price and quantity (size).

Hope this helps.

Well if you have some good long-term ideas let me know, my tool stack is in its infancy as well really.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants