Talk:NPLB K300 Drive 1

I saw the note about waiting until the end of the drive to update the data table. A few questions and comments:

1. Why do we have the data table for this drive and not most other drives? Other RPS drives added and dropped k's and do not have such a table. It would be nice to have more consistency in how the drive pages are created. I feel like a set of standards is needed for them.
2. Should we wait until the end of the drive to add any more k's? I could add all of our current k's now and then add any additional k's later on as they are added to the drive.
3. Should we wait until the end of the drive to add any more primes? Currently I have just added k's that have primes.

Gary Barnes (talk) 19:27, 1 May 2024 (UTC)

to 1.: There's much to do in this Wiki and I got not the time yet to include more data from the old RPPDb pages (see RPS Drive #1 there). As shown at those old pages some statistics for every k-value is possible, also a contributor-stats table, too. Including all current k-values into that table involved in this drive could be done, otherwise they also available from the category at the bottom.

to 2.: If's not worth the time to update the k-value pages and the drive page. I suggest to wait until the drive ended and fill in all found primes then, and also the #candidates/ranges done.

to 3: same as 2. Karbon (talk) 07:59, 2 May 2024 (UTC)

OK, how about we set a standard for this? For all drive pages in the Wiki, we will establish a data table just like the one you have started here. Some data may not be applicable like number of candidates, which may not be known. We will include in the table what is applicable to each drive.

If you say that is the way to go, I could starting doing this for some of the drive pages with fewer k's like the RPS 1st & 3rd megabit drives and eventually move on to drive pages with more k's.

If I know what all kind of things you want to include in the drive pages, I can get them done.  :-)

Gary Barnes (talk) 03:15, 3 May 2024 (UTC)