submarine

You should initialize the state.data Try like this.

self.__dict.values() is a list of lists, not a single list of positions. So you're comparing a string to a list, and this will never be true.

You need to drill down another level:

You where almost there ;) Just add the background-color: #2b6a83 to your :before and :after elements. Be aware that an :after element with a position absolute will be rendered in front of the parent element. You can fix that by using a simple negative z-index like z-index: -1:

Maybe try and redesign your logic if I understand correctly:

Right now, you choose a spot for a certain ship of a certain length. But why do you need to choose more spots for your ship?

Instead, have two more radio buttons that will determine the orientation of the ship: one for horizontal orientation and one for vertical orientation. This way, when a player choose a spot, the buttons automatically highlight either in the horizontal or vertical direction with of course the correct amount highlighted. Example: a ship of length 4 was chosen and horizontal orientation was chosen. Now the player chooses 3, 2 (assuming 3 is the third row and 2 is the second column) on the grid. 3, 3; 3, 4; 3, 5 also highlight red along with the chosen to show where the ship will be located.

To highlight the correct amount, you can utilize for loops. Loop for the chosen ship’s length and then increment either the column, c, if horizontally is chosen or row, r, if vertically is chosen and set all those buttons to red i.e

Svg better to be inside div so you have more control on the shape and it's also can be scale.

First I fix your path 'd' with this site (https://aydos.com/svgedit/)

Second I put the svg inside the div

Third I order the svg with view box to suitable (with color red some transparent) like the background-image link in 'bearing_lead_disc' and use css pointer-events:none for ignore clicking on the div and then we can rotate the circles even we clicked on the shape.

link: (https://codepen.io/omergal/pen/qBqzeQa)

pic:

If you are working with spacy you should make your text a spacy type, so something like this:

I think you'll find that the biggest difference between the two modeling problems is the nature of the survey data. Clearly, it is much easier to survey terrestrial elevation data (using airborne lidar or even old-fashioned surveying techniques) than marine environments. For practical reasons, bathymetric surveys using sonar will often be collected in the forms of "track lines" such as those shown in the figure below. Sometimes, the geometry of the data collection will introduce artifacts into your models.

Also, if you are working with a closed body of water, such as a lake or reservoir, you will absolutely have to consider introducing shoreline data using a Constrained Delaunay triangulation. The picture below illustrates what happens if you don't.

I've posted a couple of wiki articles that talk about using the Delaunay to model lake volume and reservoir capacity. You may find that some of the ideas they discuss will help you to clarify some of your own ideas. The first article, Using the Delaunay to Compute Lake Volume introduces some of the principles. The second article Using the Delaunay to Create a Reservoir Volume Model gets into some of the special problems such as near-shore analysis. The pictures I've included with this post come from those articles.

Hope some of this helps.

The board is valid if the position of all of the ships are valid.

This means you need a data structure for the ship. To start, a simple data structure might be [ ship_type, [ position_1 , position_2, position_3 ] ]

Once you have data structures for the ship, it is trivial to check that all of the ships are on the board, no two ships share a single position, and the correct number of ships of each type are on the board. Correct number of ships of each type can go into a Fleet data structure.

With a ship, you will quickly realize that the board for the side with awareness of its fleet can be rendered with letters for their ships. But the other board is "special" because there is no ship visibility. This means that (as in the real game) Battleship consists of two kinds of board, a hit-detection board and a ship positioning board. That they look similar is only a side-effect of manufacturing.

Now for the HitBoard how would and AI attempt to hunt down a ship? Well, they would start off with random placements, or a pattern. There are advantages to both approaches. Once a hit is detected, then it will consult the number of remaining ships on the field, and start probing along the horizontal and vertical axis to find the ship's full position. Once it is told "You sunk my " It will know that the sunk ship must be removed from play.

In order to achive that, you can work with percentages, so if you reduce the scale of the window the size of the images reduce as well.

CSS: