<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
	<channel>
		<title>Dealing with coding setbacks.</title>
		<link>/blogentry/186100</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/186100" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: Dealing with coding setbacks.</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: Dealing with coding setbacks.</title>
			<link>/blogentry/186100</link>
			<guid isPermaLink="true">/blogentry/186100</guid>
			<pubDate>Sat, 17 Aug 2024 15:52:32 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>After multiple attempts to get the follower script to work with vectors, it is apparently not simple to do with Pandas data frames.<br /><br />In the past, I would most likely have given up at this point (or maybe not even gotten as far), but now I can leverage the education to find a solution...<br /><br />Since the unique part of the vector for frequency was the signed angle, I just need to regenerate the .csv files from the spreadsheets after replacing the vectors with just their signed angle... If I need the whole vector in the future, it is simple trig to regenerate the line lengths.<br /><br />This means a full rework of 8 spreadsheet lookup tables, but after the first is reworked, the other 7 are simply copied...<br /><br />Then converting only what is needed to .csv<br /><br />Then rolling back to an earlier version of the follower program... that part is easy when using version control software like GIT and meaningful commit memos.<br /><br />So the setback is not that bad, and following software engineering best practices leads to this challenge being relatively easy to overcome.<br /><br />Speed was looking good though, the entire program did run in under 60 seconds, it just was unable to determine the appropriate follower counts.... &#x5b;&#xa0;<a href="/blogentry/186100">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/186100</wfw:comment>
		</item>
	</channel>
</rss>

