Which field define if the Order is in A-book or in B-book - fix-protocol

I'm building a FIX acceptor and in when i process a new order i want to act to different depends if the order is in A-Book or in B-Book. I can't understand qhich field may give me this information. I was thinking about HandlIndt (21) but i'm not quite sure. Anyway i would like to get a better explanation on each value of HandlInst..

Fiximate is your friend for all these sorts of questions.

There is nothing to do with standard FIX itself. You should refer to your's counterparty FIX specification. If you can share ECN name, I can try to point you to the right direction.

Related

simulating the estimatiors in matlab

I have an assignment like this but I do not know where to start( sorry I do not know much about Matlab). I have struggled with the variable C( how can I pass the value into it when its range is unknown?) and these blocks at the bottom as well. I have to do something like Simulink or just coding to achieve it. I have searched on the internet but I do not see anything related to my task. Or maybe I use the wrong keywords to find it. Could you give me some suggestion or links which are relevant to this. Thank you so much!

what is the best way to handle defines in system verilog/uvm

I have a verification component which is used by many teams. I have a define say ADDRESS_WIDTH and i set it to the max of all the requirements from all the teams.
But that does not look like the ideal solution. Is there a way this can be handled in the SV/UVM way.
I thought of couple of ways
I list this as a parameter in the agent so that people can use defparams to update it, but then also I would need a way to handle interfaces separately.
This leaves a potential hole, where someone might update one place and not change another place.
There is also a command line option to update a define, but that is not ideal solution if the parameter list is too many.
I can have a separate defines file and everyone can have their own defines file, but that would depend on the compilation order.
Please let me know what other better solutions are there.
Thanks in advance.
Use a package to define the parameters that both the interface and verification component will use and therefor keep in sync. Each team can modify the package to suit their needs.
Create another package that specifies the legal range of values for those parameters and have either the interface or verification use assertions to check the values of the team's package.

Get broken hard (or soft) constraints

Like the question says. After a
solver.solve();
I want to see specific rules (with values) that were violated. How can I get them from the solution?
The examples already do this, take a look at this method:
org.drools.planner.examples.common.business.SolutionBusiness#getScoreDetailList()
But it's not standardized yet, see this issue.

Why use MEMCACHED_BEHAVIOR_NOREPLY?

I am writing a library that wraps libmemcached.
I noticed that there is an interesting behaviour setting for memcached which says that I can indicate that I do not care about the results of my memcached commands...
It is known as MEMCACHED_BEHAVIOR_NOREPLY. Why would somebody want to use this?
It would be great if someone could point out a few use cases? multi-get / multi-set spring to mind, but I am not clear how this would be useful.
ASCII protocol noreply was a mistake. Don't use it.
Binary protocol noreply can be used to make really awesome optimizations without any loss of correctness.

Autogenerated keys in Pilog

What's the best way to go about autogenerated keys for Pilog? i've
been digging around a bit and can't find anything related.
Hints and pointers would be most appreciated. Thank you.
You get the same behavior as auto increment in for instance MySQL with this
one: http://software-lab.de/doc/refG.html#genKey
I use it a lot in the VizReader code.
I'm not so sure I would've used it much though if I had know about the (id)
function from the start: http://software-lab.de/doc/refI.html#id
In my case it's all about displaying a nice id that is easy to relate for
humans and JavaScript in my non-traditional gui and as you can see both
approaches accomplish that but that latter is imo more elegant.
/Henrik Sarvell
(Copied verbatim form Henrik Sarvells' answer.)