[megan_mcp]

Hi @may

Please see attached some documentation/blogs that might help with the topic of partitioning tables.

Partitioning Data in kdb+ | KX

Partitioned Tables – thinq-kdb (wordpress.com)

Partitioned tables | Knowledge Base | kdb+ and q documentation – Kdb+ and q documentation (kx.com)

Thanks,

Megan

[megan_mcp]

Hi @mario

This article should prove to be useful – Containerizing kdb+ with Docker. Making kdb+ portable and scalable | by Aidan O’Gorman | Medium

If you have any issues, please let me know!

Thanks,

Megan

[megan_mcp]

Hi @utsav

It looks to me like you might not have created an API key yet.

To double check this, goto the KDB.AI portal under Connection Details -> API Keys.

If you have any more issues please feel free to let me know.

Many thanks,

Megan

[megan_mcp]

Hi @masmail

The certificates get sent out every hour so it could have just took a minute but I see you have received it so congratulations on completing the course!

Thanks,

Megan

[megan_mcp]

Hi @trinity

Thank you for letting us know, as always we will make sure to update this immediately so that it is accurate for future users.

Many thanks,

Megan

[megan_mcp]

Hi @trinity

Thank you for reporting this.

We will adjust this so that it is accurate.

Any more issues feel free to let us know!

Many thanks,

Megan

[megan_mcp]

Hi @masmail

I’ve noticed a few things from your screenshots:

If you take a look at the challenge.quke file, you will see the correct answer should be as follows (screenshot below). So you don’t seem to have the correct values.

The problem lies in your table join. To be able to join two or more tables, you must use a related column. In this case our related column is ‘student_no’.

To do this I’m going to use an INNER JOIN:

"INNER JOIN students ON results.student_no = students.student_no"

Also to achieve the correct value when rounding I advise you use ROUND instead of FLOOR.

Hope this helps!

Thanks,

Megan

[megan_mcp]

Hi @trinity,

Thank you for bringing this to our attention.

You are correct and I will have this updated immediately.

Many thanks,

Megan

[megan_mcp]

 

Along with  ‘s help on how to convert to degrees, thanks for showing me a quicker way of solving it!

q)ab: 10 
q)bc: 10 
q)atan ab%bc 
0.7853982 
q)atan[ab%bc]*180%acos -1 
45f

 

[megan_mcp]

thanks so much for all the advice ! Now looking back at my own solution and your examples, I should have took advantage of using a function. I can see how using a lamba is more effective than reading in the values. I will most definitely take this on board in the future as I understand the fewer the lines of code the better debugged.

[megan_mcp]

Thank you for your reply! I forgot about the casting.

 

 

 

[megan_mcp]

Perfect! What’s more effective than one line of code?

Can you explain the start  of the code? :

q)-1 "0123456789"

 

[megan_mcp]

Thank you for sharing  !

[megan_mcp]

Hi  !

Have you had a look at the template for returnN ?

I think a key feature that you could use is sublist – Sublist of a list | Reference | kdb+ and q documentation – Kdb+ and q documentation (kx.com)

So simply order the table by the column provided in ascending order then subset the first/last N records from the newly ordered table.

If you are still unsure, please feel free to reach out.

Many thanks,

Megan

 

 

 

[megan_mcp]

Hi ,

You are correct for using kx.q.qsql.select, but maybe take a look at the below links to correct the formatting of your query.

This will output a pykx.Table which then can easily be converted to a python array.

Generating PyKX objects – PyKX

Querying – PyKX

Hope this helps!

Thanks,

Megan