| 00:08.53 | starseeker | mpictor: awesome, thanks! |
| 00:09.37 | starseeker | mpictor: yeah, that looks like it's got it with kesha's patch |
| 00:10.10 | starseeker | mpictor: I'd go for the merge |
| 00:14.29 | mpictor | done |
| 00:14.38 | mpictor | and thanks for taking a look! |
| 00:14.50 | starseeker | no problem :-) |
| 00:15.07 | mpictor | hey, you're brl-cad's cmake expert, right? |
| 00:15.24 | starseeker | we've got one additional tweak in the BRL-CAD srcs to a delete - do you want a fork/merge for that or do you just want to grab it? |
| 00:15.45 | starseeker | mpictor: more or less, for some values of expert... |
| 00:16.01 | mpictor | are there any places in brl-cad where the names of generated files aren't known beforehand? |
| 00:16.02 | starseeker | you want me to whip up a baffledCitris CMake build? |
| 00:16.14 | mpictor | let me take a look at your change |
| 00:16.16 | starseeker | winces - ah, that case |
| 00:16.35 | mpictor | nah, I think I can do baffledCitrus myself :) |
| 00:17.02 | mpictor | I've been wondering about splitting up exp2cxx's output into many smaller files |
| 00:17.26 | starseeker | That's not an easy case to handle, to be honest |
| 00:17.32 | mpictor | I didn't think so |
| 00:18.15 | mpictor | only thing I know of that autotools or plain makefiles can handle better :/ |
| 00:18.20 | starseeker | Essentially you either have to figure out what all your specific files will be and hard-code a list of all of them, or you have to bootstrap build the tool as part of the *configure* process and add an option for that tool to generate a list of files |
| 00:19.16 | mpictor | that's what I thought. I was debating making an express scanner with lemon that would print out a list of type/select/entity names |
| 00:19.41 | mpictor | or, write a bunch of cmake regex's to do the same |
| 00:19.47 | mpictor | neither sounds appealing |
| 00:19.55 | starseeker | that would be a way to go - have a simple tool that can be easily bootstrapped and run as part of the configure process... |
| 00:20.22 | mpictor | we'd still have to build re2c/perplex/lemon during configure :/ |
| 00:20.26 | starseeker | http://sourceforge.net/p/brlcad/code/57177/ |
| 00:20.37 | mpictor | no we wouldn't, it could be static |
| 00:20.59 | starseeker | right - you write a simple, no-deps C/C++ tool that gets you just what you need to deduce the file names |
| 00:21.27 | mpictor | sourceforge has pretty diffs now! |
| 00:21.35 | mpictor | I'll commit it |
| 00:22.42 | starseeker | awesome, thanks :-) |
| 00:23.07 | starseeker | should be ready to sync up BRL-CAD's src/other/stepcode with github again |
| 00:23.18 | mpictor | cool! |
| 00:23.36 | mpictor | have you guys tried out the diamond inheritance code yet? |
| 00:23.51 | starseeker | not explicitly |
| 00:23.58 | mpictor | ok |
| 00:24.05 | starseeker | (at least, I haven't) |
| 00:24.17 | starseeker | I think it plays into our importer, but brlcad is the the one who knows about that |
| 00:24.23 | mpictor | you started working on ON_Brep after I did that; I wasn't sure if that was coincedence or not |
| 00:24.30 | mpictor | k |
| 00:25.09 | starseeker | oh - yeah, coincidence |
| 00:25.56 | mpictor | Tom Thurman found a bug in the express parser, and I am not looking forward to fixing it |
| 00:25.57 | mpictor | https://github.com/stepcode/stepcode/issues/244#issuecomment-22980478 |
| 00:27.13 | starseeker | hmm - could see if nreed feels like digging at it... |
| 00:28.11 | mpictor | apparently, tom wants it fixed so he can use exppp on ap209,ap210, and ap242 before submitting them to ISO |
| 00:28.29 | mpictor | if nreed is willing to work on it, that would be awesome! |
| 00:29.08 | mpictor | tom said that exppp is the only pretty printer in existence; the commercial companies aren't interested in writing one |
| 00:29.36 | *** join/#stepcode travis-ci (~travis-ci@ec2-174-129-102-40.compute-1.amazonaws.com) |
| 00:29.36 | travis-ci | [travis-ci] stepcode/stepcode#40 (master - 6963fc5 : Mark): The build is still failing. |
| 00:29.36 | travis-ci | [travis-ci] Change view : https://github.com/stepcode/stepcode/compare/f0f5763b9cb3...6963fc515de4 |
| 00:29.36 | travis-ci | [travis-ci] Build details : http://travis-ci.org/stepcode/stepcode/builds/10777779 |
| 00:29.36 | *** part/#stepcode travis-ci (~travis-ci@ec2-174-129-102-40.compute-1.amazonaws.com) |
| 00:29.55 | starseeker | hah, cool |
| 00:30.56 | mpictor | I found travis-ci while poking around on github |
| 00:31.17 | mpictor | they even have a neat little icon that can be embedded in your README that shows whether any tests are failing |
| 00:31.27 | mpictor | needless to say, I'm holding off for now :) |
| 00:32.24 | starseeker | I don't suppose we could just tweak the exp entry for that thing in the combined schema that is failing? |
| 00:32.41 | mpictor | hmmm, I hadn't considered that |
| 00:33.04 | mpictor | I'd like to have a small schema that exposes the bug, so that we can fix it eventually |
| 00:33.20 | starseeker | we're sure it's a bug and not a legit schema mistake? |
| 00:33.42 | mpictor | if the schema is invalid, the parser ought to fail |
| 00:33.59 | mpictor | so either a bug in the parser or in fedex_plus |
| 00:34.04 | mpictor | err, exp2cpp |
| 00:35.25 | starseeker | ah |
| 00:35.53 | starseeker | give me a few minutes to update BRL-CAD for the new stepcode stuff and I'll take a look at it |
| 00:36.09 | mpictor | sure |
| 00:49.51 | mpictor | I added the commit from r_weiss |
| 00:50.28 | starseeker | awesome, thanks! |
| 00:50.35 | starseeker | mpictor: question for you in #brlcad |
| 00:59.32 | *** join/#stepcode travis-ci (~travis-ci@ec2-174-129-102-40.compute-1.amazonaws.com) |
| 00:59.32 | travis-ci | [travis-ci] stepcode/stepcode#41 (master - ec630ba : r_weiss): The build is still failing. |
| 00:59.32 | travis-ci | [travis-ci] Change view : https://github.com/stepcode/stepcode/compare/6963fc515de4...ec630badca0f |
| 00:59.32 | travis-ci | [travis-ci] Build details : http://travis-ci.org/stepcode/stepcode/builds/10778353 |
| 00:59.32 | *** part/#stepcode travis-ci (~travis-ci@ec2-174-129-102-40.compute-1.amazonaws.com) |
| 03:17.52 | *** join/#stepcode kimzzzz (~AndChat31@1.38.24.132) |
| 05:08.14 | kimzzzz | brlcad: merged the commit I was working on 5hrs ago |
| 05:29.27 | brlcad | kimzzzz: okay |
| 05:29.31 | brlcad | which commit was that? |
| 05:30.11 | kimzzzz | I mean the issue was closed |
| 05:30.22 | kimzzzz | #254 merge I guess |
| 05:32.55 | kimzzzz | Are u free after 2 hrs ? Shall I ping u then ? |
| 05:34.24 | brlcad | kimzzzz: I just realized who you are |
| 05:34.52 | kimzzzz | Kesha here :p |
| 05:34.56 | brlcad | I'm zzzz in like 5 minutes |
| 05:34.59 | brlcad | i know that now |
| 05:35.09 | brlcad | so are you done with your open stepCode tasks? |
| 05:35.21 | kimzzzz | Yuppp |
| 05:35.27 | kimzzzz | :D |
| 05:37.24 | brlcad | okay, great |
| 05:37.29 | brlcad | do you have a fresh brl-cad checkout? |
| 05:37.50 | brlcad | do you know how to compile brl-cad? |
| 05:38.02 | brlcad | have you compiled brl-cad recently? |
| 05:38.21 | brlcad | are you familiar with geometry converters? |
| 05:38.32 | brlcad | waits for answers ;) |
| 05:40.26 | kimzzzz | I have freshly checkout version and I had also compiled abt a month or two before .. |
| 05:40.58 | kimzzzz | Geometry converters , not exactly ! :( |
| 05:41.50 | kimzzzz | I can compile the fresh copy. Hopefully it will not be an issue |
| 05:45.03 | brlcad | so yeah, make sure you compile, understand how to build our step-g geometry importer (make step-g) |
| 05:45.17 | brlcad | build it and learn how to use it |
| 05:45.34 | brlcad | learning is going to require a mix of talking to people in the channel, asking questions, and reading manual pages |
| 05:46.00 | brlcad | there is lots of information spread about regarding the importers/exporters but they all are very very similar |
| 05:46.26 | brlcad | they're all named either g-EXPORTFORMAT or IMPORTFORMAT-g |
| 05:46.36 | brlcad | they all take options and usually give usage if you just run their name |
| 05:48.07 | brlcad | spend less than an hour reading through this: http://brlcad.org/w/images/6/66/Converting_Geometry.pdf |
| 05:48.51 | brlcad | run some of the examples it talks about, find geometry on the web and try it in our NON-STEP importer/exporters |
| 05:50.05 | brlcad | tons of example geometry around the web but not all of it is "SOLID GEOMETRY", which is what we specialize in |
| 05:50.31 | brlcad | again, that document talks about that issue some |
| 05:50.47 | brlcad | you following everything so far? |
| 05:51.10 | brlcad | don't hesitate to say no or ask questions |
| 05:52.26 | kimzzzz | Yes, I am following the words but will b able to respond better when I get hands on it. . |
| 05:52.28 | brlcad | if it takes you more than a couple hours to read that doc, one or two man pages, and learn how to run the converters... |
| 05:52.39 | brlcad | it'd be an indication your'e doing something horribly wrong or inefficiently |
| 05:54.51 | kimzzzz | Okay.. right now I am in lecture. After 2 hrs it would complete. . Catch u then |
| 05:55.22 | kimzzzz | From cell.. cant really type much nw ;) |
| 05:56.01 | brlcad | that's fine, it should be plenty to keep you busy |
| 05:56.32 | brlcad | the goal is to quickly learn how to run the step-g importer |
| 05:57.07 | brlcad | you're going to need to download and install the 7.22.0 release of BRL-CAD for comparison |
| 05:57.42 | kimzzzz | Thanks. This shouldn't take too long. |
| 05:57.52 | brlcad | you'll run the 7.22.0 step-g on some model(s) that you find that DO work ... then run them in the trunk build of step-g and see if they STILL work |
| 05:58.21 | brlcad | discuss in #brlcad |
| 06:13.21 | kimzzzz | Do I need to install any others CAd software for exporters/importers ? |
| 06:14.48 | kimzzzz | Or not necessary for now ? |
| 06:31.17 | brlcad | not necessary |
| 06:32.36 | brlcad | you might want to compare with how something looks in something else but if you find the models on the web, there will usually be pics posted to show you what it should look like |
| 06:32.55 | brlcad | there will be plenty that fail, you're looking for several that'll succeed in 7.22.0 |
| 06:32.59 | brlcad | then try thos in the latest |
| 10:51.21 | *** join/#stepcode kimzzzz (~AndChat31@1.38.24.132) |
| 11:21.24 | starseeker | kimzzzz: I'd suggest looking for simple models - more complex models are more likely to run into trouble with 7.22.0 |
| 11:55.48 | *** join/#stepcode kesha (~kesha@14.139.122.114) |
| 12:21.54 | *** join/#stepcode kimzzzz (~AndChat31@1.38.24.132) |
| 13:19.19 | brlcad | starseeker: should she go farther back? |
| 13:55.01 | starseeker | brlcad: um. Probably - I think we have to go back before the conversion to std::string, whenever that was |
| 14:05.18 | brlcad | oof, okay |
| 14:06.52 | brlcad | kimzzzz: let me know when you're back around, first step is to find a version before we made that change, and set up a test |
| 14:29.57 | starseeker | brlcad: presume the idea is to identify regressions from our "best working point" and fix them? |
| 14:47.41 | brlcad | not really |
| 14:48.03 | brlcad | the idea was more to figure out whether the diamond hierarchy parsing works or breaks anything that was working |
| 15:08.21 | *** join/#stepcode kimzzzz (~AndChat31@1.38.24.132) |
| 15:15.30 | *** join/#stepcode kesha (~kesha@14.139.122.114) |
| 15:49.09 | starseeker | brlcad: oh - for that, I think 7.22.0 should work |
| 15:49.50 | brlcad | that much I know, if you think there's some breakage that happened further back, she can search |
| 15:50.55 | starseeker | brlcad: well, legend has it that an earlier state of step-g was able to import things we currently can't.. |
| 15:51.20 | starseeker | probably would have been at the tail end of Keith's initial push |
| 15:51.52 | brlcad | alright, well shouldn't be hard to quickly check that |
| 15:53.23 | starseeker | has a vague memory that he was never able to fully duplicate what Keith could demonstrate, but that's something to check anyway... |
| 15:53.56 | starseeker | as usual, "commits or it didn't happen" |
| 15:56.22 | brlcad | yep |
| 16:01.07 | *** join/#stepcode kesha (~kesha@14.139.122.114) |
| 16:01.22 | *** join/#stepcode kesha (~kesha@14.139.122.114) |
| 16:58.00 | *** join/#stepcode kimzzzz (~AndChat31@1.38.24.132) |
| 18:26.41 | *** join/#stepcode kimzzzz (~AndChat31@1.38.30.217) |
| 20:03.40 | *** join/#stepcode kesha (~kesha@14.139.122.114) |