loopy | A tool for thinking in systems

the solution if anybody is interested :)

You can transform your datetime objects into timestamps. Then, construct pd.Interval objects and iter on a generator of all possible intervals combinations for each ID:

Try:

You can use a sliding_window_view and check if the flipped view is identical. This solution is fully vectorized (non-loopy) but creates one additional array with size (len(a)-n,n).

Try:

This is essentially a matrix block operation which you can generalize from a simple matrix operation. Your example is good because you defined your block matrices as such (I renamed them A_p and u_p to not conflict with matrix u):

while(true) is (usually) not a good idea. You should call the dequeue function after you enqueue a message. The dequeue function should end when 1. there is already a dequeue function running 2. no more message in the queue.

Sounds like they are probably signing the paymentToken, not the entire message. Perhaps try something like this:

You need to make what you do to draw the tank with a new value of dato into a function. Also add a bit to it so it makes an AJAX call to get the next value of dato.

Then, once you have the initial page loaded you can set a timeout of 2 seconds and call the function again and so it goes on.

Note: I don't recommend setInterval just in case something goes wrong and takes too long. If you use setTimeout each time then you know you haven't got any other requests waiting to be serviced and you can't get in a muddle. The timeout will only be set when you've had a response. In a real life situation you'll need to think through more about what to do if the backend stops responding, or sends rubbish data.

After the initial load of the page, after 2 seconds the call is made to the same url but with a parameter dato=true The backend PHP looks to see if this is set and if it is it doesn't resend the whole page it just sends what it thinks the current value of dato is.

Because I don't have access to your database I have put in a couple of lines of code to send a random value between 0 and 100 so you can see the tank level changing. Also in the JS the L value is updated with dato, but should that be some liter sort of value rather than a %? Perhaps two values need to be sent, the % fullness and the actual volume? If so then sending them as JSON may be the answer.

Here's the altered backend code. It uses jquery's AJAX method (which does have a JSON option should you need it). For a short time this will be available on tanktemp so you can see it working immediately.