Skip to main content



Machine Learning Part 5

In this blog, we will describe another example that utilize KMeans & Spark to determine locations.

Before that, we would suggest you to got to previous blogs -

In this blog, we will analyze and try to make predictions on Fire detection GIS Data- https://fsapps.nwcg.gov/gisdata.php

  1. We will have historical data of Wild fires.
  2. And, we will try to analyze. That is eventually helpful to reduce response time in case of fire, reduce cost, reduce damages due to fire, etc.
Fire can grow exponentially based on various factors like - Wild life, Wind Velocity, terrain surface, etc. Incident tackle time is limited by various factors one of which is moving firefighting equipment. If we are plan in advance where to place equipment's such that it is close to a fire prone area. It is possible to reduce response time.

So, we can analyze the historical data and try to group them in a cluster, which has a centroid. This centroid can be helpful to determine location to make water tanks, keep fire equipment's, etc. As, this location will be close to the locations where fire has affected in past. 

K-Means is a clustering algorithm that fits suitable in this scenario and we will try to use the same.

Mostly, what we have seen a simplistic singular pipeline. But, we can have a pipeline implemented as per Rendezvous Architecture, where-in, multiple models can be applied to an request, and a user defined logic can be applied to return the best fit results to requester.  For example, We might want to locate a correct GPS address for some grocery store, or in case of Fire: we may require to alert a Fire site which can reach the location quickly, rather than the location which is close to Fire. So, an incoming request may be required to optimize with different models for different objectives. Like - Speed vs Accuracy.

We will discuss more about Rendezvous Architecture in future blogs.

This example is pretty much same as what we have seen in previous blog. But, Refer - @ https://github.com/dinesh028/SparkDS/tree/master/src/indore/dinesh/sachdev/forestfire/

Next Blog - https://techdevins.blogspot.com/2019/12/machine-learning-part-6.html

Comments

Popular posts

Unix Server ( Edge Node ) hangs when there are many jobs running on hadoop cluster started from Unix Edge Node.

  When a unix server or an edge node is running lots of jobs (like Spark, Hadoop, or custom batch processes), crashes happen. For example. For example a process might hit a segementation fault, memory issue or ay other runtime issue. By default, if ulimit -c is not 0, the OS will create core dump. Core dump are written to disk and can be very large, sometimes hundreds of MBs or even GBs per process. What we realized was that when multiple processes crash at the same time, the system suddenly tries to write core files to disk. This was leading to DisK I/O spikes. Thus, node was becoming unresponsive. This was also leading CPU spike because OS was handling crash logging. Setting "ulimit -c 0" disables core dumps. This way we lose ability to debug crashes via core dump But, kept production edge nodes stable. On most Linux systems, by default, "core dumps" are written in current working directory of the process that crashes. Linux allows you to change core dump file nam...




VPN testing checklist

 To test: Is VPN active? Is it leaking? Does it look residential? Does it alter network fingerprints? Public IP Test (Basic Detection) - curl ipinfo.io DNS Leak Test - nslookup google.com MTU Test (Encapsulation Detection) - ping 8.8.8.8 -f -l 1472 TCP MSS Inspection - Use Wireshark and Look for SYN packets. Traceroute Path Test - tracert 8.8.8.8 WebRTC Leak Test - browserleaks.com/webrtc IPv6 Leak Test - test-ipv6.com Latency / Jitter Test - ping -n 50 8.8.8.8. VPN usually causes: More Jitters and Latency. Reverse DNS (PTR Record) - nslookup <your-public-ip> IP Reputation Check - Like most IP's from VPN Providers like Express VPN, etc. are blacklisted and all. Look for: Proxy/VPN classification, Hosting provider tagging




Spark-JDBC connection with Oracle Fails - java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name

  While connecting Spark with Oracle JDBC, one may observe exception like below -  spark.read.format("jdbc"). option("url", "jdbc:oracle:thin:@//oraclehost:1521/servicename"). option("dbtable", "mytable"). option("user", "myuser").option("driver", "oracle.jdbc.driver.OracleDriver") option("password", "mypassword"). load().write.parquet("/data/out") java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208) ...




Agentic AI Development- Optimization- Bedrock Claude

Most of the models which you wish to invoke via AWS Bedrock, GPT, Google, etc, charges per token ( words/ characters ) For example -  A model like Claude is not a computer program that executes instructions. It is a statistical pattern matcher trained on text. It has no CPU, no memory, no ability to run code. It only predicts the next most likely token based on patterns it saw during training. But, some AI platforms give the model a sandboxed Python environment to actually execute code. Bedrock does have a Code Interpreter tool in Bedrock Agents — but that's a completely different setup- the overhead of setting it up just to decompress JSON makes zero sense when simply sending clean JSON is trivially easy. Easy Way To Estimate Your Cost- Step 1 — Measure your actual prompt size: Take your evidence JSON + instructions Paste into: https://platform.openai.com/tokenizer (OpenAI's tokenizer is close enough for estimation) It will tell you exact token count Step2 - Cost calculation C...




Spring MongoDB Rest API not returning response in 90 seconds which is leading to client timeout

  We have Spring Boot  Rest API deployed in Kubernetes cluster which integrates with MongoDB to fetch the data.  MongoDB is fed with data by a real time Spark & NiFi job.  Our clients complained that for a request what they send they don't have response within 90 seconds. Consider it like an OMS ( Order ManagEment System).  On further analysis, we found that Spark & NiFi processing is happenning within 10 seconds after consuming response data from Kafka. Thus, initally out thought was that it due to delay from upstream to produce data in to Kafka.  Thankfully, our data had create / request  timestamp, and when response was received, and when response was inserted into MongoDB. Subtracting response insert time from request time seemed to be well within 90 seconds. But, still client did timeout on not seeing a response within 90 seconds. This led to confusion on our side.  But, then we realized it was due to Read Preference . We updated this...