At long last some of the wildflowers I planted last year are blooming. I can see that there are frequently bees on them, so hopefully they are being pollinated.

I would like to collect wildflower seeds from flowers that I would like to propagate and then spread them over bare patches to try and fill them in. How do I recognize when the seeds are ready to be harvested? How do I harvest them, just yank the bloom off of the stem? I planted a flower assortment with:

Purple Giant Hyssop, Dwarf Columbine, Siberian Wallflower, Shasta Daisy, Lance-Leaved Coreopsis, Sweet William Pinks, Purple Coneflower, Blanketflower, Gayfeather, Blue Flax, Perennial Lupine, Russell Lupine, Maltese Cross, Dwarf Evening Primrose, Mexican Hat, Dwarf Red Coneflower, Black-Eyed Susan, Moss Verbena

I probably will spread them after the first frost so they grow in the spring.

Could someone recommend examples of high-fidelity, best-practices Western Blots from Open Access Papers? I would like to use these examples to see what kind of distortions or corruption might occur to these images when they are reproduced or archived in various ways.

I create an open source software modular synthesizer out of a Raspberry Pi Pico. You can see a video on it at https://www.youtube.com/watch?v=252Vte4tYh0

Last week my landscaper mowed down the mostly perennial, but a few annual wildflowers I was growing from seed. The landscape thought they were weeds because they were mostly not flowering yet (and there were a few weeds in there as well). So now what do I do? I have been watering it every day to see if I can grow some of the plants back. I put a lot of seed down, I hope something will last.

I have a program (fldigi, pointed to by the github link) that uses dozens of shared libraries. I would like to be able to distribute a pre-compiled version of the program for testers. I could require each tester to install the shared libraries and compile the program for themselves, however, this would be extremely difficult for most users. What are some options for distributing a pre-compiled version of a linux program? Do I need to make a package for common distributions or common versions of each distribution? How about snap, nix, or flatpak? I don't have much experience with using docker or preparing docker containers, and the particular program (fldigi) requires access to system hardware to function, which a containerized version would have to accommodate.

This is going to be a temporary solution and I hope once the program is done being tested, my changes can be pulled upstream and then distributions will include it that way.

I made a poster of my eclipse photos taken in southern Illinois. The PDF of the poster is downloadable as a 24 by 36 inch poster.

It seems to me these giant grants to a small number of organizations (Climate United Fund, Coalition for Green Capital, Power Forward Communities) seems like it could be delivering pork to well-connected people. Is this actually going to produce "clean" energy and help disadvantaged people? These seem like very large awards to a small number of organizations.

I would like to get plots started with perennial flower seeds. However, it seems like the weeds will overgrow the plots while the perennial seeds get started.

Could I mix perennial and annual flower seeds and have the annuals try and crowd out the weeds while the perennials take root and come back next year more strongly? Or will the annual seeds prevent the perennial seeds from growing?

Headline this morning on CNN's web site.

This is a demonstration if the GuitarPico's effects. The GuitarPico is an open source effects pedal. The hardware and software is available at

https://www.github.com/profdc9/GuitarPico

I'm having so much fun making this I thought I would share.

I am working on a simple, cheap, easy to construct multi-effects guitar pedal based on the Raspberry Pi Pico microcontroller. All of the other parts are generic parts. So far I have implemented the following effects:

Noise gate, Delay, Room, Combine Effects, Bandpass Filter, Lowpass Filter, Highpass Filter, Allpass Filter, Tremolo, Vibrato, Wah, Autowah, Envelope, Distortion, Overdrive, Ring Modulator, Flanger, Chorus, Phaser, Backwards (play the last few samples backwards), Pitch Shift, and Octave (rectification).

Some effects can be cascaded inside the device. There are up to 16 "units" where each processing stage can process the results of the last stage. Various controls on the effects can be assigned to the four potentiometers at the bottom of the board, or two expression pedals you can plug into the side.

I also added a VGA output because I want to have a cool video display that changes with the audio. Also, perhaps implement some kind of guitarsynth or MIDI control.

Anyways this has been a lot of fun to make. I hope others will enjoy it too.

https://www.github.com/profdc9/GuitarPico

For the past few days I've been working on a 3-D printable footpedal potentiometer to be used in a guitar pedal. It is a parametric model in FreeCAD. It has a top and bottom that hinge together, with a potentiometer that is coaxial with the hinge so that when the pedal is pressed, the potentiometer is rotated.