0

I am trying to make Chained TP to write tplog file as well.

However, what i can see from the process log is l every second. refer to this link:https://github.com/KxSystems/kdb/blob/master/tick/chainedtick.q in the shell script i already pointed out which tp to subscribe.

I changed these two functions:

if[system"t";
 .z.ts:{.u.pub'[.u.t;value each .u.t];@[`.;.u.t;@[;`sym;`g#]0#]}; 
  upd:{[t;x] t insert x;if[l;l enlist (`upd;t;x);j+:1];}]

if[not system"t";  
   upd:{[t;x] .u.pub[t;x];if[l;l enlist (`upd;t;x);i+:1];}]

also added

  .u.tick[src;.z.x 1];

at the end.

still trying to figure out why nothing in the tplog?

Terry
  • 523
  • 9
  • 21

1 Answers1

1

.u.tick (or .u.l which is defined in .u.tick) are not defined in chainedtp.q. .u.tick can be found in tick.q.

AquaQ Analytics' TorQ infrastructure has a chained TP process, which allows you to specify on startup whether you want a logfile to be created or not. More info can be found here. (Full disclaimer, I’m an employee of AquaQ).

Cathal O'Neill
  • 2,522
  • 1
  • 6
  • 17
  • so i just added tick:{init[];if[not min(`time`sym~2#key flip value@)each t;'`timesym];@[;`sym;`g#]each t;d::.z.D;if[l::count y;L::`$":",y,"/",x,10#".";l::ld d]}; and will work? – Terry Dec 22 '20 at 14:06
  • `.u.ld` is used in that function as well so it may need to be defined. I think some of the what `.u.tick` is redundant EG applying `g# attribute since that's already being done. – Cathal O'Neill Dec 22 '20 at 14:12