Noticing on the quick start guide, for the happy_birthday.py example, the localhost:8000/documentation route appears to be broken (returning 404).

Perhaps I'm doing something wrong, but if not, we should fix the bug and/or the documentation. And maybe consider an integration test as part of our test suite to prevent a future regression.

Is your feature request related to a problem? Please describe.
According to the Arrow spec:

Bitmaps are to be initialized to be all unset at allocation time (this includes padding).

This would imply that bits outside the range [0, size) should always be zero. However, in cuDF/libcudf, we take a more conservative approach and say that bits outside [0,size) are undefined in order to a

When using artm.SmoothSparseThetaRegularizer(tau=tau_val) with tau_val<0 we get some \Theta matrix columns filled totally with zeros. From perplexity score, the optimization converges. The quantity of documents with all zeros in their \Theta columns grows as $tau_val->-\infty$.
How it's possible that optimization constraint on theta columns violates?

What are the requirements to build the documentation?

If I call make, I get this error:
sphinx-build2: command not found

Maybe some instructions could be added to the README?

Thanks for the nice repo.

I have been looking into how to manually translate IDL files (or perhaps write a tool at some point to do so) to the required ctypes definitions used in this library, but I'm somewhat confused as to how sequences are handled. Are you supposed to represent something like this:

struct SomeElement
{
    string someData;
    // ... and some other fields
};

struct SomeKey
{
    unsign