⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 2004-october.txt

📁 acis说明文档
💻 TXT
字号:
From Nilesh.Joshi at asu.edu  Wed Oct  6 21:50:12 2004From: Nilesh.Joshi at asu.edu (Nilesh Joshi)Date: Wed Oct  6 21:55:01 2004Subject: [Acis-alliance] STEP 203Message-ID: <IKEJINCPIFDAJOBCMLDKGEGNCIAA.Nilesh.Joshi@asu.edu>hias the built in step converter in ACIS wont give me the relationship betweenthe faces represented in STEP and those in ACISi am trying to write my own converter from ACIS to STEP which is much easierthat the other way round.But, obviously I am not able to find out where my mistake is in the STEPfile.I have a conical hole in rectangular part.But, the step file i generated shows cylindrical hole and non manifoldgeometryi have attached the file along.can anyone tell me what wrong and how do i find out in the future as what'swrong?With Regards-Nilesh JoshiDesign Automation LaboratoryArizona State University*Engineering problems are under-defined, there are many solutions, good, badand indifferent. The art is to arrive at a good solution. This is a creativeactivity, involving imagination, intuition and deliberate choice. - Ove Arup-------------- next part --------------A non-text attachment was scrubbed...Name: sw_test9.STEPType: model/stepSize: 13277 bytesDesc: not availableUrl : http://lists.cs.columbia.edu/pipermail/acis-alliance/attachments/20041006/6ebd5953/sw_test9.binFrom Christian.Pietersen at uk.radan.com  Thu Oct  7 10:52:46 2004From: Christian.Pietersen at uk.radan.com (Christian Pietersen)Date: Thu Oct  7 10:53:16 2004Subject: [Acis-alliance] access violation error in api_hook_annotations()Message-ID: <PEEFJOALJDHPOPDGPCGEKEGHDCAA.Christian.Pietersen@uk.radan.com>HelloI keep getting access violations in api_hook_annotations() and have not beenable to get to the bottom of the problem and would like to know if anybodyelse has had similar problems and have found what the cause is.Basically on recalling a model in a new session, the first call toapi_hook_annotations() fails with (result).quant == 1015 which is an accessviolation. This gets handled correctly and the failure does not effect themodel in any way. Recalling the model in the same session doesn't suffer thesame problem, it only happens on the first ever call toapi_hook_annotations()  in any modelling session.To me this sounds like an initialisation problem but I can't see any problemin our code.I could ignore this problem as it seems benign but I'm concerned that it isa symptom of something else that could be more serious so I'd like to solveit and would really appreciate any comments, suggestions or ideas.ThanksRegardsChristian-----------------------------------------------------------------------------------Here is how we turn annotations on       {              // Get acis to create annotations       outcome result = api_set_int_option("annotations", TRUE);       UTC_ASSERT(result.ok());       result = api_set_int_option("unhook_annotations", FALSE);       UTC_ASSERT(result.ok());              // hook annotations required for addressing       result = api_hook_annotations();       UTC_ASSERT(result.ok());       m_annotationsAreOn = true;       }And here is how we turn them off and reset.       {       if (m_annotationsAreOn)        {               // unhook annotations required for addressing        outcome result = api_unhook_annotations();        UTC_ASSERT(result.ok());               // Clear annotations required for addressing        result = api_clear_annotations();        UTC_ASSERT(result.ok());        result = api_set_int_option("unhook_annotations", TRUE);        UTC_ASSERT(result.ok());               // and switch the option off        result = api_set_int_option("annotations", FALSE);        UTC_ASSERT(result.ok());        }       m_annotationsAreOn = false;       }------------------------------------------------Radan Computational Ltd.The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only.  If you have received this message in error or there are any problems, please notify the sender immediately.  The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden.  Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd.  The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.-------------- next part --------------An HTML attachment was scrubbed...URL: http://lists.cs.columbia.edu/pipermail/acis-alliance/attachments/20041007/587c0150/attachment-0001.htmlFrom bsatishn at ford.com  Mon Oct 11 05:56:06 2004From: bsatishn at ford.com (Satishnaidu, B (B.))Date: Mon Oct 11 05:56:44 2004Subject: [Acis-alliance] Error while evaluating distance from the point to	the surface Message-ID: <B6BD9B1D57778A46891C3F1850C0B93F02EAD55A@AP1SGM51.SINGAPORE.FORD.COM>Hi Friends,I am getting the following Error while evaluating distance from the point to the surface using  " api_entity_point_distance() " function.can anybody help me why this error is coming ?. Is the Surface is not proper or any other reason?. I checked the surface continuity , it looks good and maximum (C0) distance is 0.035mm.Error details:************************************************************************* coincident face_face_ints with different body vertices (spaacis/src:BODY_VERTEX_CRUMBLE)**********************************************************************RegardsSatish-------------- next part --------------An HTML attachment was scrubbed...URL: http://lists.cs.columbia.edu/pipermail/acis-alliance/attachments/20041011/b286b9f4/attachment.htmlFrom xpqian at engin.umich.edu  Tue Oct 19 10:48:16 2004From: xpqian at engin.umich.edu (Xiaoping Qian)Date: Tue Oct 19 10:48:44 2004Subject: [Acis-alliance] ACIS on Windows-Cygwin gccIn-Reply-To: <Pine.GSO.4.58.0405102036020.20582@alumni.engin.umich.edu>References: <20040511002551.GB1124@softwehr.net>	<Pine.GSO.4.58.0405102036020.20582@alumni.engin.umich.edu>Message-ID: <Pine.GSO.4.58.0410191047160.25299@alumni.engin.umich.edu>Folks,Can we develop ACIS based applications on Windows-Cygwin with gcc asopposed to VC++?Thanks,Xiaoping Qian.From Ray.BAGLEY at Spatial.Com  Tue Oct 19 12:02:18 2004From: Ray.BAGLEY at Spatial.Com (Ray.BAGLEY@Spatial.Com)Date: Tue Oct 19 12:02:41 2004Subject: [Acis-alliance] Ray Bagley/dassault-systemes is out of the office.Message-ID: <OF3F9BB60A.8B0A7EBE-ON87256F32.005819FD-87256F32.005819FD@Spatial.Com>I will be out of the office starting  10/12/2004 and will not return until10/27/2004.I will respond to your message when I return (perhaps sooner if theethernet gods are kind to me).  Please contact my manager, Linda Lokay, at303-544-2911 for urgent matters.From prwolfe at sandia.gov  Thu Oct 21 08:57:51 2004From: prwolfe at sandia.gov (Wolfenbarger, Paul R)Date: Thu Oct 21 08:58:30 2004Subject: [Acis-alliance] ACIS on Windows-Cygwin gccMessage-ID: <BCD6BEF0CD0AE546B84C1848C5F255A90A164C@ES23SNLNT.srn.sandia.gov>I have worked in cygwin, but you still have to use cl instead of gcc dueto differing ABI's.  I think this may be less of an issue with gcc 3,but I have not tried it.  Also be very careful in building your makefileto use the same flags that Spatial does or cl can actually give youincompatible binaries!Paul -----Original Message-----From: Xiaoping Qian [mailto:xpqian@engin.umich.edu] Sent: Tuesday, October 19, 2004 7:48 AMTo: acis-alliance@cs.columbia.eduSubject: [Acis-alliance] ACIS on Windows-Cygwin gccFolks,Can we develop ACIS based applications on Windows-Cygwin with gcc asopposed to VC++?Thanks,Xiaoping Qian._______________________________________________Acis-alliance mailing listAcis-alliance@cs.columbia.eduhttp://lists.cs.columbia.edu/mailman/listinfo/acis-allianceFrom pedro.vcm.oliveira at gmail.com  Fri Oct 22 12:38:58 2004From: pedro.vcm.oliveira at gmail.com (pedro oliveira)Date: Fri Oct 22 13:51:31 2004Subject: [Acis-alliance] Re: From gi/gl husk to HOOPS?Message-ID: <51d6d43e0410220938c96b306@mail.gmail.com>Hi,At this time I am having the exact same problem and it seems It seemssome of the old functionality of gihusk will have to be handimplemented as the event handling from hoops is quite different. Ijust wanted to know if in the mean time you were able advance and, ifso, if could provide me with some guidelines regarding the process.Greetings    Pedro Oliveira>Hi dear ACIS fans,>>I'm porting our application from ACIS 7 to the most recent ACIS 12 SP5.>>One thing that disturbs is, that spatial no longer supports the gi/gl husk>and suggests instead to use the newer HOOPS for visualization purposes.>>Since i'm not very familiar with gi/gl let alone HOOPS i'm now searching>some kind of tutorial or cross reference to move from gi/gl to HOOPS.>>Any help welcome>>Greetings>MarkusFrom pedro_oliveira at bigfoot.com  Sat Oct 23 13:35:16 2004From: pedro_oliveira at bigfoot.com (Pedro Oliveira)Date: Sat Oct 23 13:35:49 2004Subject: [Acis-alliance] Re: From gi/gl husk to HOOPS?Message-ID: <417A9654.1010505@bigfoot.com>Hi,At this time I am having the exact same problem and it seems It seemssome of the old functionality of gihusk will have to be handimplemented as the event handling from hoops is quite different. Ijust wanted to know if in the mean time you were able advance and, ifso, if could provide me with some guidelines regarding the process.Greetings   Pedro Oliveira >Hi dear ACIS fans, > >I'm porting our application from ACIS 7 to the most recent ACIS 12 SP5. > >One thing that disturbs is, that spatial no longer supports the gi/gl husk >and suggests instead to use the newer HOOPS for visualization purposes. > >Since i'm not very familiar with gi/gl let alone HOOPS i'm now searching >some kind of tutorial or cross reference to move from gi/gl to HOOPS. > >Any help welcome > >Greetings >MarkusFrom Markus.Herb at de.TRUMPF.com  Mon Oct 25 04:16:28 2004From: Markus.Herb at de.TRUMPF.com (Markus.Herb@de.TRUMPF.com)Date: Mon Oct 25 04:17:12 2004Subject: [Acis-alliance] AW: From gi/gl husk to HOOPS?Message-ID: <71A23A253EBDD711933A00B0D0F0B13105BC22E7@srvmail2.corp.trumpf.com>Hi Pedro,I'm sorry but, we have postponed the porting to HOOPS.Instead we have requested the sources of the gl/gi husk from spatial.So we are able to still use it with ACIS 13 now.I would suggest to contact spatial support in order to request the sourcestoo.If you go the other way and use HOOPS, please keep me uptodate with your progress, since we still plan to use it later too.GreetingsMarkus> -----Urspr?ngliche Nachricht-----> Von: Pedro Oliveira [mailto:pedro_oliveira@bigfoot.com] > Gesendet: Samstag, 23. Oktober 2004 19:35> An: acis-alliance@cs.columbia.edu> Cc: markus.herb@de.trumpf.com> Betreff: Re: From gi/gl husk to HOOPS?> > > Hi,> > At this time I am having the exact same problem and it seems > It seems some of the old functionality of gihusk will have to > be hand implemented as the event handling from hoops is quite > different. I just wanted to know if in the mean time you were > able advance and, if so, if could provide me with some > guidelines regarding the process.> > Greetings>    Pedro Oliveira> >  >Hi dear ACIS fans,>  >>  >I'm porting our application from ACIS 7 to the most recent > ACIS 12 SP5.  >  >One thing that disturbs is, that spatial no > longer supports the gi/gl husk  >and suggests instead to use > the newer HOOPS for visualization purposes.  >  >Since i'm > not very familiar with gi/gl let alone HOOPS i'm now > searching  >some kind of tutorial or cross reference to move > from gi/gl to HOOPS.  >  >Any help welcome  >  >Greetings  >Markus> 

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -