magnets | crawls funny pictures from various websites via node.js

I have a question regarding the bittorrent protocol: Assume we have a private tracker where we register and login to download torrent files/access magnets. We know that clients announce to the tracker to get a list of peers and then the client itself connects to different peers to download separate pieces of the whole file. Once the client finishes downloading or aborts, it sends an AnnounceFinished message to the tracker for stats/graceful shutdown of the client.

Now, let's say the tracker wants to maintain a download/upload rate (like it's commonly done in real trackers) to limit leechers from downloading too much without uploading. How does the tracker get real/legitimate statistics about the download/upload volume of a peer when the actual download/upload only happens between the peers themselves? Do they need to be honest and cooperate and send the right stats to the tracker or can the tracker somehow enforce the correct data?

Suppose I have an object that I'd like to convert into an array of objects, retaining the object keys as properties for each nested object.

In this simple example, any of these would work:

I have code like this. It uses JSoap library. I am getting titles, magnets, seeds, leechers (these two together as TorrentStats) from torrent site. Now I want to merge them inside one List, of course it's pretty easy to do it in standard for loop but is there any way to map or flatmap them in stream?

I want to count the number of different magnets that are in my table.

They´re defined by a string of around 20 elements, of which I´m interested in the first five.

All of them have the same pattern:

I would like to create several pdf files in rmarkdown.

This is a sample of my data:

I am trying to convert my data into a html document using Rmarkdown, and I am currently relying on conversion to vectors and indexing to solve my problem.

Although my sample data has 4 observations, my actual datasets has over 30 records, so indexing seems cumbersome and unnatural.

Is there a better way to pull out each of these elements in sequence? Any suggestions would be great.

I have a docstring in the beginning of every module describing its usage and functionality. Here I also want to add the most relevant parameters - like settings in a parameter file or via command line arguments. It's no classical function parameters since the module might be called as stand-alone as well (via if __name__ == '__main__' capture). But since the ordinary parameter formatting of Sphinx is neat I want to just re-use it.

However, Sphinx seems to handle the "Parameter" section differently when in a module compared to when in a function.

This is how they are formatted differently:

You see the difference. In functions the keyword "Parameters" is added and then we have a nice bullet list. In modules no title is created, no list, the type is not set in braces but on an additional line etc.

Docstring format is the same (numpydoc):

I've been working on a simulation of a magnetic pendulum (Magnetic Pendulum for reference). Now, I have a question concerning how you calculate the forces/acceleration:
In examples you find online of the magnetic pendulum (such as the one provided above), and other physics force and acceleration calculations, the forces are calculated at a starting position, the position updated according to time-step dt and then new forces at time t+dt calculated to get a new position and so on. Basic numerical integration, makes sense.

However, I noticed, that if I calculate the forces this way, things don't go as one would expect. For example: when the pendulum is attracted by a magnet it just stops at the particluar magnet even tough you would expect it to "overswing" a bit. Therefore, I introduced three variables for each force which is all previous forces added together, and now it somehow seems to work correctly. I'm wondering if

1. the way of calculating the forces I used makes sense in a physics simulation and
2. if not, then what am I doing wrong? Because it seems to work for other people.

Here's my code:

I am trying to make an animation where two magnets (that are repelling each other) are falling in a rotating tube. I have the falling (gravity) bit and rotation down but I am having trouble with magnetic forces. The equation for the force that I am using is (magnetic strength of magnet 1 x magnetic strength of magnet 2)/(distance between the magnets)^2. Basically, the strength of the force decreases with the square of the distance between the magnets. The goal is to have magnets repel each other as the same poles are facing each other. I believe I am not using the "apply_force_at_local_point" command properly. I am especially unsure about updating the x and y directions of the forces in the "apply_force_at_local_point" command

You really don't need to know much physics for this. Thanks for the help in advance