Observation 216150: Conocybe tenera group

Proposed Names

39% (3)
Eye3 Eyes3
Recognized by sight
-4% (3)
Recognized by sight: Lets not use Conocybe tenera group for any Conocybe even when there is the distinct possiblity its not even remotely related to C. tenera or not (No way to even start to know without seeing caulocystidia).

Please login to propose your own names and vote on existing names.

Eye3 = Observer’s choice
Eyes3 = Current consensus


Add Comment
By: Byrain
2015-11-05 13:15:03 PST (-0800)

If anyone wants to post some scoped Conocybe, I am willing to put it through the keys in the book given enough information is available. I haven’t spent much time looking into it yet, just enough to get the impression that I know almost nothing about the genus besides the basics and the concepts in the books even with species like C. apala don’t necessarily match up with what we would consider common knowledge. I have a few of my own collections I want to scope, but I’m a bit preoccupied with school and life at the moment. I wonder how much we share with Europe for Conocybe species? There are papers with DNA suggesting that the C. apala collections in the states are not the same as the European counterparts.

As for the the ringed species, I think they all fit cleanly into Pholiotina sect. Pholiotina, at least according to FAN6.

There are a few others I’d use
By: Christian (Christian Schwarz)
2015-11-05 08:54:30 PST (-0800)

Brown-capped species (tenera group), Pale-capped species (apala group), Blue-footed species (cyanopus group), Golden-capped species (aurea group), and depending on your phylogeny, Ringed species (filaris group).

We could also work on making other macro-morphologic concepts and correlating them with specific species. This idea of ‘Recording aggregates’ is something I have written about before, and which eBird has put to good use:

There are a number of people in California who are interested in this genus of mushrooms, and who have the technical ability to make excellent photos and record and illustrate microscopic details.

All it takes is for those folks to start differentiating the Conocybe they find in California and giving us provisional names and identification criteria.

Create a project on MO!
Make species lists!
Write dichotomous keys, and link to them as PDFs!

Amateurs can make inroads on these sorts of questions. At this point in time, there isn’t much obstructing the path of taxonomic progress for an interested and motivated amateur.

Byrain – you’re well qualified to significantly modernize our understanding of California’s Conocybe. But the community needs more help in getting educated about what you are discovering!

Sounds good.
By: Jacob Kalichman (Pulk)
2015-11-05 08:10:07 PST (-0800)
Broad sense?
By: Byrain
2015-11-05 07:14:44 PST (-0800)

As in half the Conocybe in the ~1000 pg. Conocybe/Pholiotina book? We should probably call the other half Conocybe apala group.

I think Conocybe tenera group
By: Alan Rockefeller (Alan Rockefeller)
2015-11-04 19:49:59 PST (-0800)

is a fine name for any similar looking Conocybe, as long as the name is used in the broad sense. It is the “field guide name”.

This gets back to
By: Christian (Christian Schwarz)
2015-11-04 14:24:27 PST (-0800)

Nathan’s proposal some time ago for a semantic vernacular for fungi.
Since it never moved forward (it would be a lot of work), we are left with the haphazard use of names like Conocybe tenera group that stand in for what would likely have been “Brown Conehead” in the semantic vernacular. Not the best solution, but it works pretty well within the confines of MO.

…which is a specific concept.
By: Jacob Kalichman (Pulk)
2015-11-04 14:21:02 PST (-0800)
It implies some specific concept.
By: Byrain
2015-11-04 14:15:25 PST (-0800)

We don’t have one for this other than “Brown Conocybe”.

Who says “group” implies monophyly?
By: Jacob Kalichman (Pulk)
2015-11-04 14:12:45 PST (-0800)

Created: 2015-09-14 10:16:59 PDT (-0700)
Last modified: 2015-11-05 15:31:54 PST (-0800)
Viewed: 97 times, last viewed: 2016-10-22 12:41:20 PDT (-0700)
Show Log