skuep / gds3d Goto Github PK

In order to use GDS3D with the remote filesystem structure over slow connections, compression (server-side) and decompression (client-side) would be nice.

For this, XZ compression should be used. The start scripts will have to be adapted in order to decompress the gds files, in case compression is used. In the skill script, compression should be available optionally.

Hi Skuep,
Thank you for the software. I am facing any issue while highlighting nets in gds with a custom file ( needed as layer structure , sequence and height etc is requried). But I realized that if use default example.txt, it doesn't highlight nets. Any help will be appreciated.

Regards
Abhishek Dwivedi

make: Entering directory '/home/neha1010/GDS3D/linux'
g++ -c -w -O1 -I ../math/ -I ../gdsoglviewer/ -I ../libgdsto3d/ main.cpp -o main.o
In file included from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
../libgdsto3d/gds_globals.h:98:9: error: reference to ‘byte’ is ambiguous
98 | byte RecordType;
| ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
from /usr/include/c++/11/vector:60,
from ../libgdsto3d/gds_globals.h:34,
from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’
404 | enum class byte : unsigned char;
| ^~~~
In file included from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
../libgdsto3d/gds_globals.h:94:23: note: ‘typedef unsigned char byte’
94 | typedef unsigned char byte;
| ^~~~
../libgdsto3d/gds_globals.h:99:9: error: reference to ‘byte’ is ambiguous
99 | byte DataType;
| ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
from /usr/include/c++/11/vector:60,
from ../libgdsto3d/gds_globals.h:34,
from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’
404 | enum class byte : unsigned char;
| ^~~~
In file included from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
../libgdsto3d/gds_globals.h:94:23: note: ‘typedef unsigned char byte’
94 | typedef unsigned char byte;
| ^~~~
../libgdsto3d/gds_globals.h:100:9: error: reference to ‘byte’ is ambiguous
100 | byte *Data;
| ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
from /usr/include/c++/11/vector:60,
from ../libgdsto3d/gds_globals.h:34,
from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’
404 | enum class byte : unsigned char;
| ^~~~
In file included from ../gdsoglviewer/windowmanager.h:29,
from main.h:24,
from main.cpp:29:
../libgdsto3d/gds_globals.h:94:23: note: ‘typedef unsigned char byte’
94 | typedef unsigned char byte;
| ^~~~
make: *** [Makefile:31: main.o] Error 1
make: Leaving directory '/home/neha1010/GDS3D/linux'

It seems at the moment, only the layer numbers can be specified in the techfile. However, some technologies also make extensive use of the purpose property. This makes in some cases the result useless, because non-fabricated layers get render together with the actual material.

linux/GDS3D: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory

Hey guys, thanks a lot for this awesome piece of software. Many of my colleagues have been using this to make great artwork.

Now, I have a problem which may be completely my own fault. I generated a GDS file from Python, with code similar to gdspy (https://github.com/heitzmann/gdspy)

I made the process file and try to run GDS3D, but it gets stuck in the command line at 'Opening GDS file ...'. Nothing shows up.
This is on Windows. I tried the example included in the downloaded package and that one does work. I also tried the example gds with my own process file and that works too. So I think it's an issue with my GDS file. Now, I've been able to open the GDS file in KLayout. So there's something in there, but maybe the file is corrupt or something, I just don't know what it could be.
I also noted that the Windows terminal in which I run the command is using a lot of CPU (even if nothing shows up).

Any idea what the problem may be?

Thanks!

Maarten

I've been really struggling with the UI. In particular, it is very easy for my entire layout to vanish off of the screen. As an example, I have a fairly small layout. Pressing r centers the layout and gives me a view looking straight down on it as if I had placed a wafer under a microscope. w and s are like turning the microscope zoom knob in and out respectively.

a and d however act like the following. Pretend the wafer is sitting on top of a very tall cylinder and I tip the cylinder left (d) or right (a). What I see is the tipping but only tipping by a small number of degrees causes the layout to leave the screen to the left or right and I can't seem to figure out how to pan (in my microscope analogy, slide the cylinder that the wafer is sitting on top of left or right) to get the image back on screen.

q and z have a similar problem as a and d but it is tipping forward/backward instead of left/right. But again, I only have to tip a little bit before the entire layout is off the screen.

So what it looks like is that the reference point for the rotation is much too deep into the screen so instead of seeing my layout rotate left/right/up/down, I see a large amount of motion that overshadows the rotation part.

Between not being a c++ programmer (C yes, C++ no) and having no GL experience at all, I'm struggling a bit to really understand the code. However the comment here jumped out at me a little as maybe relevant.

If only there were a key press that would slide the whole think back under my virtual microscope!

Any suggestions? This is so close to working for me but not just quite.

It is super useful to be able to look at what the side view of a cross section would look like. This would be an extremely powerful feature.

When making figures for papers and so forth, the background looks better as white. It would be cool if this feature existed. I may work on it if I get time.

After Installing all packets GDS3D need, made the following sentence from a example I found:

/GDS3D -p onc18.txt -i Prop2_v1.gds
I got:
[root@---]# Program received signal SIGSEGV, Segmentation fault.
Program received signal SIGSEGV, Segmentation fault.
0x000000000040a2da in Wm_X11::main(int, char**) ()

Debugging with gdb:

Program received signal SIGSEGV, Segmentation fault.
0x000000000040a2da in Wm_X11::main(int, char**) ()
....

(gdb) bt
#0 0x000000000040a2da in Wm_X11::main(int, char**) ()
#1 0x000000000040a77e in main ()

Please, could you give any help?

Thanks.