Showing results for 
Search instead for 
Did you mean: 

RE: [personal kdb+] Abridged summary of

New Contributor

Thanks Caolan,

I appreciate the follow up. I managed to get things working, so thanks for the help.  I also found the following works in sending entire scripts by reading and razing the text from a .q file.


Follow up question – what I noticed is I have to remove all comments from my for it to work properly  (i.e. no // prefixed lines even if I include a semi-colon.)  While it works, it would be ideal to leave comments in the code for auditing  Am I missing something regarding the comments?


Many thanks again!




\p 5042

h:hopen `:XXX.XXX.XX.XX:5042

funcsraze read0[`$"./Functions/MyFunction.q"] /(Note** -  I had to remove all comments from my function code fyi as it didn’t like // at all.)  

h funcs

hclose h





Sent: Monday, October 26, 2020 6:47 AM
To: Abridged recipients
Subject: [personal kdb+] Abridged summary of - 3 updates in 3 topics


·      matrix convolution - 1 Update

·      Best practices setting up KDB+ server architecture? - 1 Update

·      how to generate multiple columns - 1 Update

Devon McCormick <>: Oct 24 06:32PM -0400

Thanks for the help. I may look at the Fourier transform if what I have is
too slow but I want to complete the process all the way to the end before I
worry about optimizing it. Does anyone have

Caolan rafferty <>: Oct 24 03:23PM +0800

Hi Jason,
You can pass function definitions across IPC like so:
q)h:hopen 5555
q){h({x set y};x;value x)}each value "\\f";
On 6 Oct 2020, at 00:12, Charles

Alvi Kabir <>: Oct 22 08:52PM -0700

Another approach: Build up column dictionary and pass it into functional
q)show t:([]date:.z.d-til 100;close:100?100f)
date close
2020.10.23 54.97936

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to




New Contributor III
New Contributor III
Hi Charles,

You can read any remote file/script in as a byte stream using 'read1' and then subsequently use '1:' to write this byte stream to a local file (along with comments)

q)`:local_script.q 1: `:hostname:port"read1`:remote_script.q"