PolyM | PolyM is a very simple C++ message queue | Messaging library

It's hard to say for sure without seeing the the full source code example, but it sounds like the problem you're facing is related to JavaScript not inferring this as the context for calling instance methods in the same way that e.g. Java does. To make things more complicated, this wouldn't have the expected value inside the function that you create for the click listener.

One way around that would be to use an arrow function since they aren't redefining the execution context:

Vaadin 19 requires vaadin-button version 2.4.0. Your addon requires the same version so there is no conflict and only one version will be used.

Vaadin 20.x.x requires vaadin-button version 20.x.x. which is not compatible with your addon.

The easiest solution is to bump the version of the vaadin-button in your addon to 20:

I find it easier to use the Axes object returned by the pandas plotting method and set the y tick label alignment to 'center':

I think you don't want a polynomial for the whole surface: that's likely to be very unstable, with huge amounts of variation between the points.

However, you might want a low degree local polynomial fit, or some low degree interpolation.

You haven't posted your real data, so I'll demonstrate with fake data. First, we do interpolation between the points:

Self-avoiding walks has been studied at least since the 1960s and there's a vast literature on them. Fortunately, the problem you face belong to the simplest ones (walks' length is fixed at a relatively small value).

The first thing you should be aware of is that your question is too broad to have a unique answer. That is, if you plant many polymers in the system, the result you're going to get depends on the dynamics of the polymer planting and growing. There are two major cases. Either you plant a number of seeds and start growing polymers from them, or you grow each polymer "elsewhere" and then try to plant them in the system at a random location, one by one, keeping the condition of self-avoidance. The two methods will result in statistically different distributions of polymers, and there's nothing you can do about it, except to specify the system dynamics in more detail.

I believe the second approach is a bit easier, as it saves you from deciding what to do if some polymers cannot grow to the desired length (restart the simulation?), so let's focus just on it.

The general algorithm might look like this:

• Set maximum_number_of_attempts to reasonably large, but not too large a value, say a million
• Set required_number_of_polymers to the required value
• Set number_of_attempts to 0
• Set number_of_planted_polymers to 0
• While number_of_attempts < maximum_number_of_attempts AND number_of_planted_polymers < required_number_of_polymers
  • increase number_of_attempts by 1
  • generate the next random polymer
  • chose a random position (lattice site) in the system
  • check if the polymer can be planted at this position without intersections
  • if and only if yes,
    • accept the polymer (add it to the list of polymers; update the list of occupied lattice nodes)
    • increase number_of_planted_polymers by 1

To speed thing up, you can be choosing the initial positions only from unoccupied sites (e.g. in a while loop). Another idea is to try and use a polymer, on its first plating failure, several times (but not too many, you'd need to experiment) at different positions.

Now the next step: how to generate a self-avoiding random walk. Your code is almost OK, except for a few misconceptions.

In function void Grid::plant_polymer there's one grave error: it always performs the search in the space of possible polymer shapes in exactly the same order. In other words, it is deterministic. For Monte Carlo methods it sounds like a disaster. One thing you might do to handle it is to randomly shuffle the directions.

One thing that you can certainly do to improve performance is to force moving _G rather than coping it to G:

Should we create it manually under the project directory

Yes. Maven plugin does not generate it automatically as the folder is normally in our archetypes and project starter templates.

Go to cypress.json and write. This makes sure that all your get and find queries automatically go through shadow dom's without explicitly mentioning it.