ChrisOfBristol

The closest result to hugin-ptx is https://hugin-ptx.narkive.com , the posts on this are 4 years old, so I conclude that it has been archived. However, I have subscribed to hugin-ptx@googlegroups.com and to panotools-devel mailing list. I'm guessing that align_image_stack pulls together several tools from Panotools, and enables me to make a statement which includes filenames and several parameters - without align_image_stack I couldn't do that, so that is where I should be looking for answers. "not...

The closest result to hugin-ptx is https://hugin-ptx.narkive.com , the posts on this are 4 years old, so I conclude that it has been archived. However, I have subscribed to hugin-ptx@googlegroups.com and to panotools-devel mailing list. I'm guessing that align_image_stack pulls together several tools from Panotools, and enables me to make a statement which includes filenames and several parameters - without align_image_stack I couldn't do that, so that is where I should be looking for answers. "not...

I'm not sure of the relationship between these. I get the impression that SourceForge-Hugin is now managing all three, so this repository would now be redundant, is that correct? I have a Linux Flatpak application which uses align_image_stack, which depends on: - wxWidgets - libpano13 - ilmbase - openexr - vigra - exiv2 - boost Are all these really necessary? In particular wxWidgets is quite something to include - especially since I'm using AIS from a command line call so I can't see why I should...

There was some discussion about this sort of thing on the other thread https://sourceforge.net/p/veroroute/discussion/general/thread/fd9d231587/?page=1 There is an HTML file here https://github.com/PopoutApps/qucs_netlist the first paragraph from it is: "Valid Components A selection of useful Qucs components was chosen (see list below) and a schematic containing them all drawn called qucs-netlist.sch . The components were then associated with gEDA VeroRoute components as there is a reasonable selection...

There is an HTML file here https://github.com/PopoutApps/qucs_netlist the first paragraph from it is: "Valid Components A selection of useful Qucs components was chosen (see list below) and a schematic containing them all drawn called qucs-netlist.sch . The components were then associated with gEDA VeroRoute components as there is a reasonable selection of them and their component names are valid in VeroRoute, so a netlist using them can be imported. Component sizes were not considered as Qucs components...

There is now a Python package available from PyPI called qucs-netlist https://pypi.org/project/qucs-netlist/ which can take a QUCS schematic and simulation file (or create the latter if necessary) and convert them into a netlist suitable for loading into VeroRoute (or DIY Layout Creator or any other PCB layout software that can load a standard netlist). There is a discussion about it here https://sourceforge.net/p/veroroute/discussion/general/thread/fd9d231587/ which was started before the qucs-netlist...

There is now a Python package available from PyPI called qucs-netlist which can take a QUCS schematic and simulation file (or create the latter if necessary) and convert them into a netlist suitable for loading into DIY Layout Creator, VeroRoute or any other PCB layout software that can load a standard netlist. Available from here https://pypi.org/project/qucs-netlist/ Also on GitHub here https://github.com/PopoutApps/qucs_netlist

There is now a Python package available from PyPI called qucs-netlist https://pypi.org/project/qucs-netlist/ which can take a QUCS schematic and simulation file (or create that the latter if necessary) and convert them into a netlist suitable for loading into VeroRoute (or DIY Layout Creator or any other PCB layout software that can load a standard netlist). There is a discussion about it here https://sourceforge.net/p/veroroute/discussion/general/thread/fd9d231587/ which was started before the qucs-netlist...