9 thoughts on “Introduction to MAD (video)”

    1. I hope to offer OSX support. I was able to get the core code running on my mac here, but it was an adventure to get all the python prerequisites installed correctly. I have a way to package all the dependencies up into a single standalone binary, but I don’t know anything about creating a .dmg for distribution. If anyone out there can help me with that process, please let me know!

  1. Hello Curtis,
    I cloned it from git, open an example (it happens to all examples) Saved it and started Detailed Build and got following error message:

    skipping rear trim
    Traceback (most recent call last):
    File “/home/xxx/opt/madesigner-master/creator/creator_ui.py”, line 234, in build_detail
    circle_points=32, nest_speed=”nice”)
    File “/home/xxx/opt/madesigner-master/creator/builder.py”, line 54, in __init__
    self.load(filename)
    File “/home/udo/opt/madesigner-master/creator/builder.py”, line 505, in load
    wing = self.parse_wing(wing_node)
    File “/home/xxx/opt/madesigner-master/creator/builder.py”, line 466, in parse_wing
    wing.build()
    File “/home/xxx/opt/madesigner-master/lib/wing.py”, line 254, in build
    pos = rib.trim_front_wedge(flap.pos, flap.angle)
    File “/home/xxx/opt/madesigner-master/lib/structure.py”, line 161, in trim_front_wedge
    bx = self.find_flap_bottom_front(cutpos, angle)
    File “/home/xxx/opt/madesigner-master/lib/structure.py”, line 149, in find_flap_bottom_front
    bx = self.contour.intersect(“bottom”, (tx, ty), wedge_slope)
    File “/home/xxx/opt/madesigner-master/lib/contour.py”, line 322, in intersect
    b1 = pt[1] – m1 * pt[0]
    TypeError: unsupported operand type(s) for -: ‘NoneType’ and ‘float’

    I am running it on Ubuntu 14.04 with the 3.19 kernel. Is there any chance that you can help me? Cause it looks like a good working and useful tool.

    Regards
    Udo

  2. Hi Udo,

    Thanks for trying madesigner. I just tried running the latest version from git on the first example file and was successful. Can I ask what version of python you are running? I have:

    $ python –version
    Python 2.7.12

    It is possible to see similar errors if you’ve specified some inconsistent set of features (i.e. intersecting spars, or a spar cross section bigger than the rib, etc.) Physical problems like this can sometimes blow up the math, but the examples should all work. Are you seeing this issue on the first example?

    Thanks,

    Curt.

  3. Hi Curt,
    I use Python 2.7.6

    When I use your example01 everything works fine. But as soon as you change the Rootairfoil to naca2412 and the tipairfoil to naca4412 then you can see in the terminal by using detailed build:

    Failed to fit: WL1
    Part (1000.0×174.117840796in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR1
    Part (1000.0×174.117840796in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL2
    Part (1000.0×151.830935835in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR2
    Part (1000.0×151.830935835in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL3
    Part (1000.0×129.410675383in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR3
    Part (1000.0×129.410675383in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL4
    Part (1000.0×107.355616604in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR4
    Part (1000.0×107.355616604in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL5
    Part (1000.0×85.4039098806in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR5
    Part (1000.0×85.4039098806in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL6
    Part (1000.0×64.0767971779in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR6
    Part (1000.0×64.0767971779in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL7
    Part (1000.0×42.3265822511in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR7
    Part (1000.0×42.3265822511in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL8
    Part (1000.0×20.8056755284in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR8
    Part (1000.0×20.8056755284in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL9
    Part (1000.0×2.93449647186in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR9
    Part (1000.0×2.93449647186in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL10
    Part (1000.0×23.035172318in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR10
    Part (1000.0×23.035172318in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WL11
    Part (1000.0×44.3971963537in) exceed size of sheet (24.0×12.0in)
    Failed to fit: WR11Part (1000.0×44.3971963537in) exceed size of sheet (24.0×12.0in)
    wing: made a (bad) stringer shape with only 2 points!
    wing: made a (bad) stringer shape with only 2 points!

    and if you try to view the .ac file you will find only crappy lines 🙂

    It seems to me there is anywhere a result of “endless”

    And I want to try exactly the combination from 2412 to 4412 cause this is often used by modell aircombat models.

    chers
    Udo

  4. Hi Udo,

    I was able to take a look this morning and observed that the airfoil data file parsing code was struggling with the naca2412.dat file which had a slightly different syntax variation compared to most of the other airfoil files. I’ve pushed a small change to the airfoil parser and hopefully this will get you back up and running again.

    Thanks for the feedback and bug report!

      1. You should be able to do a “git pull” to update your version if you cloned from the master repository on github. Otherwise if you created you own fork, I’m not sure how that work. Github must have some magic to sync with upstream updates?

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.