TILES | community discovery in dynamic social networks | Machine Learning library

Right now, you're defining the size of the ellipses based on a transformation of sin(y). A transformation means it looks like a * sin(b * y + c) + d, and in this case you have

• a = tileSize / 2
• b = 300 / 60 = 5
• c = frameCount
• d = tileSize / 2

If you want to do a different pattern, you need to use a transformation of sin(theta) where theta is the "angle" of the dot (I put "angle" in quotes because it's really the angle from the vector from the center to the dot and some reference vector).

I suggest using the atan2() function.

Solution:

Try to give the full path

Use the & parent selector like:

1. Create a state variable on Result comp to keep track of the card item that holds the lat lng info
2. Pass it as a prop to Mapbox comp
3. On the Mapbox comp create a local variable to save the map instance and use it to change the map view every time you click on a card.

divider

You have your variable assignements the wrong way around, you must write variable = value in python to give a variable a value.

So in your case, leitiko=a to create a new variable named leitiko and containing the same thing as a.

When you write a=leitiko, python is trying to give the variable a the same value as a variable name leitiko. But that leitiko variable doesn't exist, so it gives you an error.

Figured it out. For those wondering the ordering is -x to +x and z+ to z- . So a for loop such as the following will get you the right ordering. width and height here are in terms of the number of tiles/height values per row/column

The problem is with this line:

cordinates="[" + df["LAT"].astype(str) + "," + df["LON"].astype(str) +"]"

You are generating a string literal and passing that in.

Try replacing that line with:

cordinates = [(lat, lon) for lat, lon in zip(df["LAT"],df["LON"])]

This will generate a list of (lat, lon) tuples, which should work. I also don't think you need to cast them to str

As documented in the Reference under Function item types (emphasis added):

When referred to, a function item, or the constructor of a tuple-like struct or enum variant, yields a zero-sized value of its function item type. That type explicitly identifies the function - its name, its type arguments, and its early-bound lifetime arguments (but not its late-bound lifetime arguments, which are only assigned when the function is called) - so the value does not need to contain an actual function pointer, and no indirection is needed when the function is called.

There is no syntax that directly refers to a function item type, but the compiler will display the type as something like fn(u32) -> i32 {fn_name} in error messages.

Because the function item type explicitly identifies the function, the item types of different functions - different items, or the same item with different generics - are distinct, and mixing them will create a type error:

It seems that your Categoria and Child model share almost all of their attributes. The issue is that the _buildTiles expects a Categoria and the children of Categoria are Child.

If you merge the Child and Categoria models you can do as follows.