scratch

The curve_fit method doesn't support additional constraints. However, you could implement a non-linear least-squares problem

Here is the basic example of plotting data from the python flask and HTML + JS.

Python Code:

We can aggregate by first and last name. The total doses is simply the count of non NULL vaccination dates. For the total required number of doses, we can start with a value of 2. This value can then be offset by 1 assuming there exists a non NULL date for the pos column, indicating that a given person tested positive at some point.

When calculating an eigenvector you may change its sign and the solution will also be a valid one.

So any PCA axis can be reversed and the solution will be valid.

Nevertheless, you may wish to impose a positive correlation of a PCA axis with one of the original variables in the dataset, inverting the axis if needed.

If you are displaying this in a single regular monitor (Full HD) that has a 1920 x 1080 resolution you won't probably be able to display every single point.

This is because the resolution is actually the number of pixels you can represent - so your max, considering you are using the whole screen, would be 1920 pixels x 1080 pixels (~2M pixels/dots).

So, in order to represent the amount of pixels you want, in a single regular monitor you have to go with the options below:

• Group the items;
• Adding a panel with scrolling bars;
• Reduce the data set.

After you decide on your strategy, you can use the D3 javascript library to plot it.

Here you can find a good post about a strategy to group the items and them plot them using D3: https://int21.io/post/50-million-points/index.html

Following code adds a memory to the signals which can be wiped using MultiSig.reset() to reset the count of all signals to 0. The memory can be queried using MultiSig.query_memory(key) to return the number of hits for that signal at that time.

For the memory function to work, I had to add unique keys to the signals to identify them.

Good for you for trying to code a project like this from scratch! That's how I learn best too.

You're getting scrollbars because you're setting the height of the div in your #fbPost instead of letting it be determined by the content, and then you also set overflow: auto, which tells the browser to show a scrollbar if the content of a container overflows the container, and to hide the scrollbar if it doesn't. You can read more about that here

Also, as a best practice, an id is meant to be unique. So there should only be one thing in your html with id="fbPost", you shouldn't put that on each of your sections. It's better to use classes like your ourCard class to style multiple elements.

In terms of how to make the content two columns, you can just use the column-count css property.

I also recommend looking into and learning CSS Grid for layouts instead of using floats;

Here's a very basic JSFiddle showing what I'm talking about: https://jsfiddle.net/karlynelson/vd7zq8h4/29/

You can use media queries to make it go down to one column of text at a certain point, or use fancy css grid min-max and auto-fill to do it automatically.

This documentation will help you clarify your understanding on how Next.js handles automatic static optimization. Take a look at the caveats in that documentation to understand when that gets disabled at a global level.

Beyond that, whether or not each individual page behaves as SSG, ISR, SSG + CSR or SSR is a matter of the data requirements of the individual page. See this documentation to better understand the different ways Next.js handles each page depending on the data requirements.

Now, to answer your two questions directly:

1. I cannot find any indication that using Redux in Next.js disables SSG. In fact, here is an official example using Redux to illustrate both an SSG and SSR Next.js page implementation. Same goes for the react context API. On the other hand, it is entirely possible for you to unintentionally disable SSG by both using Redux / react context while requiring dynamic data in your page. Read up on the documentation linked in the second paragraph above to understand this better.

2. Fetching data from your custom NodeJS server client-side does not necessarily disable SSG. It will disable SSG if you require dynamic data on each page load. You have the choice to either statically generate your page (SSG + CSR) and then request your data client-side post page load (think axois / browser fetch API + loading indicator); OR, if you need the data to be present immediately upon page load (SSG & SSR), you can use getStaticProps + getStaticPaths to inject that data at build time (SSG) or getServerSideProps to inject the data on each page load (SSR).

Ok so after a bit of even more digging I found an answer to a different question detailing how I could interact with the /v2/trades endpoint which actually does what I need it to do.

You can find more details here, just mind the fact that the endpoint for making the original order is /v2/trades instead of /v2/trade as specified there. Otherwise, his description is accurate and works as of today.

I should also mention that I did open a ticket to Coinbase before getting this solution and their response was that they are only providing support through their public documentation which is short for "you're an idiot, it's all written there".

Needless to say that the public API documentation does not mention the /v2/trades endpoint, instead it documents the /transaction endpoint which does not work for transfers as specified in the original question.