PlanetCatfish.com

Hi Jools,

As I record data for repeat spawns, one thing that changes (usually growing or stabilizing at a higher number after initial spawns) is the egg count. Would it be worth or practical to add egg count/clutch size to the Further spawns category?

I've prepared a graphic for what it might look like (see pic). This is my data for Amblydoras nauticus, with egg count omissions being times I didn't apparently record the number of eggs. I realize that the data for number of eggs per spawn would be better compiled down by the egg info (e.g., initial egg count, egg size, egg color, days to hatching, etc), but it would certainly be convenient to record egg count with date of spawn.

Thoughts?

Cheers,
Eric

This is do-able. I could also add notes per addn spawn (I prefer not to use notes and prefer data ascribed to a property e.g. placement of eggs).

So, questions back are there any other data items that would be useful here and also would notes per spawn be utilised - if so for what.

Cheers,




Jools

Let me think about this. Some data, such days to hatching, max length at various ages, etc., will be tied together based on feeding, crowding and temperature parameters with each each spawn. Those don't intrinsically represent reproducible data but might be left as a single number such as (what is the largest size achieved at age for all your spawns). In other words, so fish grow slower one spawn and faster the next; that doesn't change what they're capable of doing, so that can be a single number which the user is encouraged to update if it changes from spawn to spawn.

But variables that are not linked from spawn to spawn such as tank size, temp, pH, hardness, conductivity, number of males/females and body length of smallest parent; body length specifically also influences gonad size and will therefore have some correlation with # eggs laid; as parents grow, so too might clutch size increase with successive spawns. I know I've observed that with many species from "first" spawn to later spawns.

So these are the types of data that are probably worth collecting in such a table form.

Thinking of the display of a BLOG page as it exists now, for any BLOG reporting a single spawn, I see no reason to reorganize the page display. But for multiple spawns, instead of itemizing dates (as is the current display for multiple spawns), could we build an expanding table with a single row of headings?

In such a case with repeated spawns, maybe it would be fine to report singular temperature, hardness, conductivity and pH values rather than ranges as is the case now. Readers can still infer the ranges by looking at variation between single values for the different events. The rest of the BLOG (remaining data and narratives) can still be displayed in text entries as they are now in current displays.

This is an incomplete thought on my part. Work is rather busy as end of semester approaches. But these are my initial thoughts without filter.

Cheers,
Eric

What is the purpose of the tank dimensions?

Cheers,

Jools

Jools wrote: ↑20 Apr 2024, 09:38 What is the purpose of the tank dimensions?

Cheers,

Jools

I was hesitant to include them, but did because if the fish are growing, they may have been moved to a bigger tank.

My guess is that in most cases they won't have been moved so I'm fine omitting that.

Cheers, Eric