The Linux readme (https://github.com/supercollider/supercollider/blob/develop/README_LINUX.md#environment) mentions the use of environment variables SC_JACK_DEFAULT_INPUTS and SC_JACK_DEFAULT_OUTPUTS as ways to decide which jack client to connect to on startup. This is a cool feature but for some reason these environment variables are just overwritten in the startup method for the linux platfo

Proposed Behaviour

None of the core VPR algorithms should care if the relevant t_physical_tile is an input / output / IO type.

Current Behaviour

Some behavior is still dependent on whether a tile is an input / output / IO type.

Possible Solution

The relevant code shouldn't need to care. Once all callsites of is_input_type/is_output_type/is_io_type are removed, the

During the work on merging #1419 I figured out that the basic BUFGMUX example works differently on Arty Board and Nexys Video.

The example uses three LEDs:

• led[2] - blinks with slow frequency
• led[1] - blinks with high frequency
• led[0] - blinks with the same frequency as led[2] or led[1] depending on sw[0] state.

On the Arty Board, the example works as intended. On Nexys Video, when