From: Mike C. <16...@bu...> - 2017-12-05 23:01:10
|
Hi Bert Sorry for my late response. Checked out your branch, compiled and ran it against gsvit2 test1. That all works. I will test a little more tomorrow. Thanks for your commitment to this! Cheers Mike On 11/26/2017 02:27 PM, Bert Timmerman wrote: > Hi Mike and all, > > I sort of finished reformatting the gsvit HID in "home/bert/LP1695534" > and it compiles without warnings. > > It needed #include "find.h" and function prototype declarations for: > > void common_draw_pcb_line (hidGC gc, LineType *line); > void common_draw_pcb_arc (hidGC gc, ArcType *arc); > > in "src/hid/common/draw_helpers.h". > > Could you please have look at the code and test functionality please ? > > TIA and kind regards, > > Bert Timmerman > -- You received this bug notification because you are a member of PCB Bug Team, which is subscribed to pcb. https://bugs.launchpad.net/bugs/1695534 Title: patch to enchance features of NELMA Status in pcb: Triaged Bug description: I am updating the NELMA export function to work with gsvit http://gsvit.net/ an open source FDTD solver with GPU computing support. Most of the translation is being done with a separate software package, pcb2gsvit https://github.com/mpcrowe/pcb2gsvit . The existing code that uses the NELMA output, NELMA-3.2, appears to be dead code and was never fully functional. I haven't tested the code changes against the original NELMA code, but I expect that it breaks it. The processing chain of (patched)pcb -> pcb2gsvit -> (patched)gsvit is producing an reasonable output. Development is far from complete, but I would like to begin the process of integrating a patch to implement the changes I've implemented so far. Changes .png layers now represent unique traces as different colors which map to a netname an xml file is now generated that provides board specific information. Remaining work includes better trace color indexing for netlist mapping to .png output of component XY(z) data (z being the side of the board component is located) Rational for implementing patch at this time Maintains coherent code base (commit early, commit often) Develop methodology of submitting patches you your group Begin dialog for developing NELMA export tool Rational for rejecting patch at this time Developers are too busy Patch needs to go in wildly different direction Patch breaks existing NEMLA tool Code changes are not complete Feature patch request needs to be requested with different venue I feel that the rational for considering this request outweighs the rational for rejecting it. Thank you for considering this request! To manage notifications about this bug go to: https://bugs.launchpad.net/pcb/+bug/1695534/+subscriptions |