Spaces:
Runtime error
Runtime error
David Wisdom
commited on
Commit
·
26d3c3e
1
Parent(s):
f3087dd
edit the wording
Browse files
app.py
CHANGED
@@ -119,10 +119,10 @@ def main(data_path: str, enc_path: str):
|
|
119 |
venice_fig = plot_venice_blvd(df, encoding_labels)
|
120 |
|
121 |
# Display the plots with Streamlit
|
122 |
-
st.write('#
|
123 |
-
st.write("""
|
124 |
stops by their geographic location.
|
125 |
-
The algorithm finds three clusters.
|
126 |
Points labeled `-1` aren't part of any cluster.
|
127 |
Clicking on `-1` in the legend will turn off those points.""")
|
128 |
st.plotly_chart(example_fig, use_container_width=True)
|
@@ -132,10 +132,14 @@ Clicking on `-1` in the legend will turn off those points.""")
|
|
132 |
I then clustered those encodings so that I could group the stops based on their names
|
133 |
instead of their geographic position.
|
134 |
As I expected, stops on the same road end up close enough to each other that DBSCAN can cluster them together.
|
|
|
|
|
135 |
Sometimes, however, a stop has a name that means something to the encoder.
|
136 |
When that happens, the encoding ends up too far away from the rest of the stops on that road.
|
137 |
For example, the stops on Venice Blvd get clustered together,
|
138 |
but the stop "Venice / Lincoln" ends up somewhere else.
|
|
|
|
|
139 |
I assume it ends up somewhere else because the encoder recognizes "Lincoln"
|
140 |
and that meaning overpowers the "Venice" meaning enough that the encoding
|
141 |
is too far away from the rest of the "Venice" stops.
|
|
|
119 |
venice_fig = plot_venice_blvd(df, encoding_labels)
|
120 |
|
121 |
# Display the plots with Streamlit
|
122 |
+
st.write('# Cluster the stops by their position')
|
123 |
+
st.write("""First, I clustered the
|
124 |
stops by their geographic location.
|
125 |
+
The DBSCAN algorithm finds three clusters.
|
126 |
Points labeled `-1` aren't part of any cluster.
|
127 |
Clicking on `-1` in the legend will turn off those points.""")
|
128 |
st.plotly_chart(example_fig, use_container_width=True)
|
|
|
132 |
I then clustered those encodings so that I could group the stops based on their names
|
133 |
instead of their geographic position.
|
134 |
As I expected, stops on the same road end up close enough to each other that DBSCAN can cluster them together.
|
135 |
+
|
136 |
+
|
137 |
Sometimes, however, a stop has a name that means something to the encoder.
|
138 |
When that happens, the encoding ends up too far away from the rest of the stops on that road.
|
139 |
For example, the stops on Venice Blvd get clustered together,
|
140 |
but the stop "Venice / Lincoln" ends up somewhere else.
|
141 |
+
|
142 |
+
|
143 |
I assume it ends up somewhere else because the encoder recognizes "Lincoln"
|
144 |
and that meaning overpowers the "Venice" meaning enough that the encoding
|
145 |
is too far away from the rest of the "Venice" stops.
|