Search
  • Sign In

Grasshopper

algorithmic modeling for Rhino

  • Home
    • Members
    • Listings
    • Ideas
  • View
    • All Images
    • Albums
    • Videos
    • Architecture Projects
    • Installations
    • Add-ons
  • Forums/Support
    • Current Discussions
  • My Page

Search Results - 【p26.pw】GoogleにあなたのWebサイトを迅速にインデックスする方法.260125105255

Topic: Update + Happy Yalda!
t. So here we go!   1. Honeybee is brown and not yellow [stupid!]... As you probably remember Honeybee logo was initially yellow because of my ignorance about Honeybees. With the help of our Honeybee expert, Michalina, now the color is corrected. I promised her to update everyone about this. Below are photos of her working on the honeybee logo and the results of her study.     If you think I'm exaggerating by calling her a honeybee expert you better watch this video: Thank you Michalina for the great work! :). I corrected the colors. No yellow anymore. The only yellow arrows represent sun rays and not the honeybee!     2. Yellow or brown, W[here]TH Honeybee is? I know. It has been a long time after I posted the initial video and it is not fun at all to wait for a long time. Here is the good news. If you are following the Facebook page you probably now that the Daylighting components are almost ready.   Couple of friends from Grasshopper community and RADIANCE community has been helping me with testing/debugging the components. I still think/hope to release the daylighting components at some point in January before Ladybug gets one year old.   There have been multiple changes. I finally feel that the current version of Honeybee is simple enough for non-expert users to start running initial studies and flexible enough for advanced users to run advanced studies. I will post a video soon and walk you through different components.   I think I still need more time to modify the energy simulation components so they are not going to be part of the next release. Unfortunately, there are so many ways to set up and run a wrong energy simulation and I really don’t want to add one new GIGO app to the world of simulation. We already have enough of that. Moreover I’m still not quite happy with the workflow. Please bear with me for few more months and then we can all celebrate!   I recently tested the idea of connecting Grasshopper to OpenStudio by using OpenStudio API successfully. If nothing else, I really want to release the EnergyPlus components so I can concentrate on Grasshopper > OpenStudio development which I personally think is the best approach.     3. What about wind analysis? I have been asked multiple times that if Ladybug will have a component for wind study. The short answer is YES! I have been working with EFRI-PULSE project during the last year to develop a free and open source web-based CFD simulation platform for outdoor analysis.   We had a very good progress so far and our rockstar Stefan recently presented the results of the work at the American Physical Society’s 66th annual DFD meeting and the results looks pretty convincing in comparison to measured data. Here is an image from the presentation. All the credits go to Stefan Gracik and EFRI-PULSE project.     The project will go live at some point next year and after that I will release the Butterfly which will let you prepare the model for the CFD simulation and send it to EFRI-PULSE project. I haven’t tried to run the simulations locally yet but I’m considering that as a further development. Here is how the component and the logo looks like right now.       4. Teaching resources It has been almost 11 months from the first public release of Ladybug. I know that I didn't do a good job in providing enough tutorials/teaching materials and I know that I won’t be able to put something comprehensive together soon.   Fortunately, ladybug has been flying in multiple schools during the last year. Several design, engineering and consultant firms are using it and it has been thought in several workshops. As I checked with multiple of you, almost everyone told me that they will be happy to share their teaching materials; hence I started the teaching resources page. Please share your materials on the page. They can be in any format and any language. Thanks in advance!   I hope you enjoyed/are enjoying/will enjoy the longest night of the year. Happy Yalda!   Cheers, -Mostapha  …
Added by Mostapha Sadeghipour Roudsari to Ladybug Tools at 3:54pm on December 21, 2013
Topic: Writing a 3dm File using Visual Studio C#
S2015 Community but I haven't been able to find the documentation for it anywhere (my google-fu is not strong). I can get the file to compile and it writes an empty 3dm document, but I want to add geometry to the document before it is written. Here is my code as it stands, I'm quite new to programming and very stuck! Any help would be appreciated. if I could get some hints as to how to include "onepoint" in the file I'd be very grateful, and I'd figure out how to write the rest from there. Thanks in Advance, Henry using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; using Rhino.Geometry; using Rhino.FileIO; using Rhino.Collections; using Rhino; namespace NurbsSurface { class Program { static void Main(string[] args) { string output = "C:/Tryitout.3dm"; File3dm nurbssurface = new File3dm(); 　 Point3d onepoint = new Point3d(0, 0, 0); nurbssurface.Write(output, 0); } } }…
Added by Henry Jarvis at 12:28am on October 7, 2015
Blog Post: A Simple simple Grasshopper-OpenOffice connector component

Well... as part of learning is also showing and discussing, I have uploaded this chunk of code that actually works.

It came out from the idea of developing an example where the theoretical…

Added by Rabindranath Andujar at 7:10am on July 15, 2011
Topic: Release Notes - Ladybug 0.0.65 and Honeybee 0.0.62
n common tasks like updating GH definitions, viewing images on the GH canvass, and augmenting existing study-types.  Most of the improvements to Honeybee have been in the making for a while and are just getting into the spotlight with this release.  Notably, a number of improvements have been made to support large-scale full building energy models, including fixes to memory issues with large models, better components for splitting building masses into zones, and the ability to store HBZones in external files.  Additionally, the THERM workflows have gotten a boost and these simulations can now be run directly from the Grasshopper canvass.   As always you can download the new release from Food4Rhino. Make sure to remove the older version of Ladybug and Honeybee before you do so and update your scripts.  So, without further adieu, here is the list of the new capabilities added with this release: LADYBUG Better Method for Updating Old Grasshopper Files - As many of you have come to realize, Ladybug + Honeybee is updated on a fairly regular basis, with a stable release roughly every 6 months and a github version that never ceases to improve itself on a weekly basis.  For this reason, we realize that updating old Grasshopper definitions to use recent components is a challenge for many of us.  While we’ve had some methods for this in the past, there were always hiccups, particularly when it came to components that had new inputs/outputs since the previous version.  Accordingly, Mostapha has added a new “Ladybug_Update File” component that will automatically update any Grasshopper Definition to be synchronized with the version of Ladybug+Honeybee that is currently in your toolbar (aka. the components in your userobjects folder).  If there is a component that has new inputs/outputs since the time you built the definition, it will be automatically circled in red in your GH definition and a newer version of the component will be automatically added right next to this component: While you still have to do some manual connecting of inputs to the newer component in this case, it should be much faster than our older methods and will hopefully help your old definitions survive long into the future!   EPWmap Now includes OneBuilding Files - Mostapha has added a number of new features to the EPWmap web interface that the “Download Ladybug” component connects to.  Among the improvements are a color wheel that quickly shows you how hot, cold, and comfortable a given climate is and, perhaps more importantly, there is now support for EPW files sourced from OneBuilding.  With the addition of many more weather files, you should now be able to use Ladybug with ease for more locations across the planet.  We should also note that the “Open EPW and STAT” component that downloads/unzips files from a URL now supports OneBuilding URLs. New Image Viewer Component - Mingbo Peng has graced Ladybug with a fantastic new “Image Viewer” component that takes a given image file on one’s machine and displays it on the Grasshopper canvas.  It also enables one to pull color data off of the image with ease by simply clicking on the pixel of the image one is interested in.  This new component is useful for a wide variety of cases, including the viewing of screenshots after they have been taken with the “Ladybug_Capture View” or “Ladybug_Render View” components.  However, many of you will likely recognize it as most immediately useful in workflows involving image-based Honeybee Daylight (Radiance) simulations.  This is particularly true as Migbo has built-in the capability to read many image file types, including PNG, JPEG, GIF, TIFF and the High Dynamic Range (.HDR) image files that Radiance Outputs: The following video gives a quick overview of the Image Viewer’s capabilities: The new component can be found under the Ladybug_Extra tab and I think I speak for us all in saying thank you Mingbo for this great component!   New Sun Shades Calculator Released Under WIP - After over a year of software development and nearly a career's worth of geometric math development, a joint effort between Abraham Yezioro and Antonello Di Nunzio has produced a new sun shade design component that can be described as nothing short of “magical.”  Based on a similar principle to the current “Ladybug_Shading Designer,” the new component takes an input of sun vectors and produces shade geometries that can block the vectors.  However, in comparison to the shading designer, the range of shade options that are available in this new component is truly staggering, ranging from classic overhangs, louvers and fins to pergolas and custom shade surfaces.  Perhaps more importantly, the calculation methods used by this new component are faster and more reliable.  It can currently can be found under the WIP section of Ladybug and it will continue to evolve in new versions of Ladybug.   Renewable Component Now Support Sandia and CEC Photovoltaics Modules - Polishing off his many contributions to the “Renewables” section of Ladybug, Djordje Spasic has added support for a couple more ways of defining Photovoltaic modules for renewables estimation.  Specifically, the Ladybug WIP section now includes components to import modules defined with the California Energy Commission (CEC) and Sandia Labs. HONEYBEE   Support for OpenStudio 2.x - A few months ago, the National Renewable Energy Lab (NREL) released a stable version of OpenStudio version 2, which included a number of improvements in stability and available features.  This stable release of Honeybee is built to work with the new version of OpenStudio and, in the coming months, Honeybee will be adding a few more capabilities to its OpenStudio workflows to support v2.x’s new capabilities.  Most notable among these will be support for OpenStudio measures.  Measures are short scripts written in Ruby using OpenStudio’s SDK to quickly edit and change OpenStudio models.  They are fundamental to visions of OpenStudio as a flexible energy modeling interface and to Honeybee’s goals of being a collaborative interface between the architectural and engineering industries.  Stay tuned for the next release for many of these new capabilities!   Critical Memory Issue Fixed for Large Energy Models - A number of you wonderful members of our community have been aware of computer memory issues with large Honeybee models for some time (examples: 1, 2, 3, 4).  Namely, a model that is larger than 50 zones could quickly eat up 16 GBs of memory and change Honeybee from a fast-flying insect to something more reminiscent of a snail.  We are happy to say that, after a much longer time than it should have taken us, we finally identified and fixed the issue.  In this version of Honeybee, such large models can now be created using less than 2% of the memory and time previously.  Thanks to all of you who made us aware of this and hopefully you will now reap the rewards of your struggle. Split Building Mass Component Getting a Makeover - Many of you veteran Ladybug users will recognize Saeran Vasathakumar as one of the original contributors of Ladybug who added components for solar fans and envelopes years ago.  Now he’s back with new components to split a building mass into zones that are truly revolutionary in their speed and methodology.  Saeran has divided the new capabilities into two components (one for floor-by-floor subdivision and another for core-perimeter subdivision) and they both can be found under the WIP section of this release. In this WIP version, core-perimeter thermal zones can only be generated for all convex and very simple concave geometries. Most concave geometries and geometries with holes (or courtyards) in them will fail. However it can handle even very complex convex geometries with speed and ease. You can expect the component to start accommodating concave/courtyard geometries very soon. Load / Dump HB Objects to File - Keeping in line with the support of large, full building energy models, this release includes full support for two components that can dump and load any HBObjects to a standalone file.  All information about HBzones can go into this file including custom constructions, schedules, loads, natural ventilation, shading devices, etc.  You can then send the resulting .HB file to someone else and they can load up the same exact zones in another definition.  This also makes it possible to have one Grasshopper file for generating the zones and running the simulation and another GH definition to import results and color zones/surfaces with those results, make energy balance graphics, etc.   Write ViewFactorInfo to File - After many of you asked for it, the _viewFactorInfo that is output from the “Honeybee_View Factor” component can now be written out to an external file using the same Load / Dump HB Objects components cited above.  For those of you who have worked with the comfort map workflows, you probably already know that calculating these view factors is one of the most time consuming portions of building a microclimate map.  Having to re-run this calculation each time you want to open up the Grasshopper script is a nuisance and, thanks to this new capability, you should only have to run it once and then store your results in an external .HB file.   Transform Honeybee Components Modified for Large Model Creation - Many large buildings today are made up of copies of the same rooms repeated over and over again across multiple floors, or along a street, etc.  Accordingly, one can imagine that the fastest way to create a full building energy model of such buildings is to simply move and copy the same zones several times.  This is what a new set of edits to the Honeybee Transform components is aimed at supporting by allowing one to build a custom set of zones, translate them several times with a Honeybee_Transform component, then solve adjacencies on all zones to make a complete energy model.   Central Plants Available on HVAC Systems - While Honeybee has historically supported the assigning of separate HVAC systems to different groups of zones, each HVAC was always an entirely new system from the ground up.  So a building with separate VAV systems for each floor would be modeled with a different chiller and boiler for each floor.  While this can be the case sometimes, it is more common to have only one chiller and boiler per building but separate air systems for each floor.  The new ‘centralPlant_’ options on the Honeybee coolingDetails and heatingDetails enable you to create this HVAC structure by making a single boiler and chiller for any HVAC systems that have this option toggled on.  Furthermore, in the case of VRF systems, you can also centralize the ventilation system, using the grouping of zones around a given HVAC to assign which zone terminals are connected to a given heat pump.   More HVAC Templates Added - As the profession continues to push the industry standard towards lower-energy HVAC systems, Honeybee intends to keep up.  In this release, we have included a few more templates for modeling advanced HVAC systems including Radiant Ceilings, Radiant Heated Floors + VAV Cooling, and Two Ground Source Heat Pump (GSHP) systems.  Variable Refrigerant Flow (VRF) systems have also gotten a large boost as it is now possible to model these systems with more efficient water-source loops.  The next release will include the ability to model central ground source systems that use hydronics for heating cooling delivery.   Run THERM Simulations Directly from Grasshopper - Anyone who has used the THERM workflow in the past likely realized that, while Honeybee can write the THERM file, you would still have to open model in THERM yourself and hit “simulate” to get results.  Now that LBNL has started a transition to becoming more open, they have graciously allowed free access for everyone to run THERM from a command line.  What this means for Honeybee is that you no longer need to open THERM at all in order to get results and you can now work entirely in Rhino/Grasshopper.  This also opens up the possibility of long parametric runs with THERM models since you can now automatically run simulations and collect results as you animate sliders, use galapagos, etc.  A special thanks is due to the LBNL team for exposing this feature, including Setphen Selkowitz, Christian Kohler, Charlie Curcija, Eleanor Lee, and Robin Mitchell.   All Options Exposed for THERM Boundary Conditions - To finish off the full implementation of THERM in Honeybee, a final component has been added called “Honeybee_Custom Radiant Environment.”  This component completes the access to all boundary condition options that THERM offers, including separate radiant and air temperatures, different view factor models, and the specification of additional heat flux (which is typically used to account for solar radiation).   Improvements to Schedule-Generating Components - Many of you who have watched the Honeybee energy modeling video tutorials have likely gotten in the habit of using CSV schedules for everything.  While this is definitely one valid way to work, it is not always the most efficient since simple schedules can be specified much more cleanly to EnergyPlus/OpenStudio and the use of CSVs can also make it difficult to share your energy models (since you have to send CSV files along with the schedules themselves).  This release adds two new schedule components that should take care of a lot of cases where CSV schedules were unnecessary.  The new “Constant Schedule” component allow you to quickly make a schedule that is set at a single value or a set of constantly repeating 24-hour values.  The second component allows you to create “Seasonal Schedules” by connecting “week schedules” from the other schedule components along with analysis periods in which these seek schedules operate.  Together, these will hopefully make our schedule-generating habit a bit better as a community. Lastly, many of you may know Mingbo Peng as the current maintainer of the Design Explorer web interface and the Colibri components under TTToolbox.  Both of these tools have been revolutionary in enabling “brute force” studies of design spaces (aka. Grasshopper scripts where one runs all combinations of a set of sliders). Now, Mingbo has graced Ladybug with the aforementioned image viewer component and it is with pride that we welcome Mingbo Peng to the development team! As always let us know your comments and suggestions.Cheers! The Ladybug Tools Development Team …
Added by Chris Mackey to Ladybug Tools at 7:30pm on July 30, 2017
Topic: The Marketing Process Of Lion King Shirt: A Prominent POD Company
ng users first across all business aspects enables them to thrive in a crowded market. From extensively researching customer needs before new product launches to optimizing shopping touchpoints for seamless omnichannel convenience, they intentionally aligns with buyer desires. This blog will explore how the company’s user-centric strategies, including research-driven innovation, frictionless shopping experiences, and targeted digital engagement, create meaningful customer connections that drive growth. By outlining the approach of this brand, this blog will help other e-commerce businesses can gain ideas and inspiration on how to place customers at the heart of their operations for long-term loyalty and sales. Marketing is the catalyst that drives business growth. Research Drives Innovation At this company, continuous market research and in-depth data analytics fuel innovation across all product launches and marketing campaigns. The dedicated marketing team studies the latest trends, customer feedback, and performance data to understand their target audience’s wants, needs, and preferences. These crucial insights directly guide and inform the development of new product collections and designs that will resonate strongly with customers and tap into rising demand. A prime example of their research-driven approach was the creation of trendy 1990s vintage collection. Extensive research assessed current fan preferences across various online communities and forums. Common requests and enthusiasm for more vintage, distressed t-shirt designs with cool, edgy styling were observed. Cross-referencing these hyper-relevant consumer insights with broader industry apparel trends forecasting rising waves of 1990s nostalgia and growth in retro distressed designs, the ingenious Lion King Shirt marketing team conceived of a 1990s throwback vintage line. Months of iterative testing and development followed as designers created numerous graphic concept variants that fused beloved characters and properties with 1990s pop culture elements into an edgy, retro vibe. Consumer testing and feedback analysis determined the best-performing designs to include in the collection. The expertly crafted 1990s vintage collection was a remarkable success upon launch, skyrocketing over 40% above initial sales projections within the first month. But beyond outstanding commercial success metrics, the strategic launch provided immense value in demonstrating a profound commitment to truly understanding its customers through dedicated research. This research-first marketing mindset now powers all ongoing design and marketing efforts across the business. Customer feedback and requests flow directly to designers to help inspire new creative concepts and products that satisfy explicit consumer demand. Sales data helps identify the most profitable niche interests, styles, and designs to double down on and expand. Lagging or underperforming products can be quickly identified, refined, or replaced in response to analytics. Even the effectiveness of real-time marketing campaigns can be optimized through analytics tracking. For example, the website heat map analysis revealed that the above-the-fold product showcase images on the home page received the most customer visual attention. In response, A/B testing began on how to best showcase the brand’s top-selling designs in that highly viewed space for an even more significant conversion impact. By continuously researching and analyzing customer needs and responses, the LionKingShirt marketing team gains invaluable consumer insights. This enables them to consistently launch relevant and resonant new products, collections, and campaigns. Their innovation is fueled by intentionally aligning content with target audiences’ desires. Just as their incredibly successful 1990s line was born out of dedicated upfront research, future product collections will similarly leverage analytics and testing to resonate with consumers powerfully. This way, research is firmly woven into the fabric of organizational culture, guiding the brand to new heights. Marketing brings innovation to life by creating demand. Seamless Omnichannel Experience This POD brand strives to create a seamless omnichannel shopping experience to meet customers wherever they engage with the brand. Great care is taken to optimize every touchpoint, from the user-friendly website to the fast mobile app, for a frictionless journey. The recently revamped website focuses heavily on showcasing products in an immersive, lifestyle way to boost impulse purchases. Product pages now feature models across diverse body types wearing the shirts in relatable settings. Customers can seamlessly zoom and swipe through high-res product images from any angle. Enhanced filtering and search help customers instantly find designs that match their style, whether they are searching by interest, color, or fit. Intuitive navigation and one-click checkout remove any speed bumps in the purchasing process. This frictionless website pairs with the Lion King Shirt mobile app, where convenience reigns supreme. Fans can browse designs and complete purchases on the go from their phones. Unexpected delays like long lines or being stuck in traffic are now filled with effortless shopping. The app’s user profile also enables personalized recommendations and push notifications about new arrivals and sales tailored to shoppers' interests. With user-friendly menus and touch controls, transactions happen in just a few taps. To deliver a cohesive experience, this start-up brand also seamlessly coordinates branding, design language, and messaging across channels beyond the core e-commerce store. Their social media profiles and email campaigns feature the same visual identity and voice as the website. This consistent omnichannel presence immerses customers in the brand whenever and wherever they engage. This unified cross-channel strategy powers growth by conveniently meeting shoppers through their preferred digital touchpoints. And with channels working in synchrony, customers feel satisfied that they can pick up any interaction right where they left off as they move between platforms. Customer retention and loyalty also strengthen as Lion King Shirt diligently optimizes based on purchase data and feedback. For example, offering integrated alternate payment options like PayPal and Amazon Pay streamlines checkout and simplifies purchases for many recurring customers. With omnichannel coordination, the t-shirt brand transforms once-isolated touchpoints into a streamlined ecosystem focused on convenience. This empowers customers to engage with the brand anywhere, anytime effortlessly. By obsessing over a smooth experience across all channels, the company builds meaningful connections that turn shoppers into lifelong fans. Marketing is the engine that propels companies forward. Targeted Digital Strategy Of Lion King Shirt This store executes a targeted digital strategy utilizing key channels like SEO, paid ads, influencer campaigns, and email marketing. Each channel plays a specific role in systematically attracting high-intent customers. Organic traffic is grown through core SEO foundations like metadata optimization, site speed improvements, and content focused on commercial intent keywords. This helps surface designs on Google for relevant user searches like “Star Wars t-shirts”. Paid advertising scales rapidly during new product launches or key seasonal events. Sophisticated PPC campaigns quickly amplify collection launches while retargeting activates previous site visitors. Social ads spotlight products to align follower interests like gaming or sports. Influencer partnerships match Lion King Tee Shirt collections with creators who appeal to the target demographic. For example, their vintage band tee designs were seeded with music influencers on Instagram and TikTok. Affiliate programs reward influencers for driving conversions while expanding reach. In addition to social media, email marketing is a crucial channel for this tee brand to nurture subscribers through personalized recommendations and promotions timed strategically around individual purchase histories. Automated post-purchase surveys inform the creation of tailored email copy and unique offer content based on direct customer feedback. Customer anniversary trigger emails surprise and delight buyers with bonus coupon codes on their yearly sign-up dates. Together, these initiatives work in tandem to engage, retain, and convert high-intent audiences from the email list. During major tentpole franchise moments or seasons like new Marvel movie releases, Lion King T Shirt strategically scales up paid advertising aggressively across channels to capitalize on timely demand signals. Meanwhile, carefully coordinated influencer seeding catches momentum on social media, with creators discussing products aligned to fan interests around major pop culture events. Email subscribers receive personalized recommendations timed to these trends, priming them for purchase. This interconnected digital strategy thoughtfully engages shoppers at each touchpoint in their journey. SEO and influencers pique awareness, while email and ads convert interest into sales. Ultimately, a flywheel effect takes hold, where new audiences discovered through one channel bring in more customers when activated through other channels. This targeted, data-led approach is the engine fueling digital growth. For fellow e-commerce companies, customer-focused strategies should spark ideas and models to evaluate and elevate the total user experience. In particular, smaller brands can apply many of the data-driven marketing tactics covered like surveys, testing, and optimization, without substantial resources. Above all, Lion King Shirt exemplifies how fixating on the user experience helps unify strategies across marketing, product development, operations and more to deliver real, lasting value to customers. Brands of any size or vertical that consistently put users first will earn loyalty and see sustainable growth unfold through word-of-mouth and retention. The POD company provides an inspirational case study demonstrating the commercial impact of true customer centricity. Keeping the user front and center fosters convenience, personalization, and relevant innovations directly driving revenues. But even more critically, it cements lasting human relationships with customers who will enthusiastically stick around for the long-term brand journey. For 21st-century e-commerce success stories, the customer experience remains at the heart.…
Added by ChrisPatt to Jackalope at 3:43am on March 27, 2026
Blog Post: Start point and curve





Added by zlyx at 4:22am on July 20, 2010
Topic: Butterfly/Openfoam floating issue
Mark/*---------------------------------------------------------------------------*\| ========= | || \\ / F ield | OpenFOAM: The Open Source CFD Toolbox || \\ / O peration | Version: v1612+ || \\ / A nd | Web: www.OpenFOAM.com || \\/ M anipulation | |\*---------------------------------------------------------------------------*/Build : v1612+Exec : buoyantBoussinesqSimpleFoam -parallelDate : May 22 2017Time : 10:18:58Host : "default"PID : 2839Case : /home/ofuser/workingDir/butterfly/simple_hvacnProcs : 4Slaves : 3("default.2840""default.2841""default.2842")Pstream initialized with:floatTransfer : 0nProcsSimpleSum : 0commsType : nonBlockingpolling iterations : 0sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 10)allowSystemOperations : Allowing user-supplied system call operations// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //Create timeCreate mesh for time = 0SIMPLE: convergence criteriafield nut tolerance 0.0001field p_rgh tolerance 0.0001field k tolerance 0.0001field U tolerance 0.0001field T tolerance 0.0001field epsilon tolerance 0.0001field alphat tolerance 0.0001Reading thermophysical propertiesReading field TReading field p_rghReading field UReading/calculating face flux field phiSelecting incompressible transport model NewtonianCreating turbulence modelSelecting turbulence model type RASSelecting RAS turbulence model RNGkEpsilonRNGkEpsilonCoeffs{Cmu 0.0845;C1 1.42;C2 1.68;C3 -0.33;sigmak 0.71942;sigmaEps 0.71942;eta0 4.38;beta 0.012;}Reading field alphatReading gReading hRefCalculating field g.hNo MRF models presentRadiation model not active: radiationProperties not foundSelecting radiationModel noneNo finite volume options presentStarting time loopTime = 1smoothSolver: Solving for Ux, Initial residual = 1, Final residual = 0.06427477, No Iterations 4smoothSolver: Solving for Uy, Initial residual = 1, Final residual = 0.06226344, No Iterations 4smoothSolver: Solving for Uz, Initial residual = 1, Final residual = 0.03950103, No Iterations 3smoothSolver: Solving for T, Initial residual = 1, Final residual = 0.03671111, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 1, Final residual = 0.008356878, No Iterations 86DICPCG: Solving for p_rgh, Initial residual = 0.07888434, Final residual = 0.0006831407, No Iterations 9DICPCG: Solving for p_rgh, Initial residual = 0.007053905, Final residual = 6.211827e-05, No Iterations 71time step continuity errors : sum local = 3777.266, global = 3.22967, cumulative = 3.22967smoothSolver: Solving for epsilon, Initial residual = 0.9994728, Final residual = 0.0532353, No Iterations 4smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.05640973, No Iterations 4ExecutionTime = 2.65 s ClockTime = 3 sTime = 2smoothSolver: Solving for Ux, Initial residual = 0.5142984, Final residual = 0.02186577, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.5242573, Final residual = 0.02244622, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.5106874, Final residual = 0.02933279, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.3832824, Final residual = 0.01046751, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.9825413, Final residual = 0.009757923, No Iterations 799DICPCG: Solving for p_rgh, Initial residual = 0.04390194, Final residual = 0.000303611, No Iterations 9DICPCG: Solving for p_rgh, Initial residual = 0.0073043, Final residual = 7.259574e-05, No Iterations 45time step continuity errors : sum local = 1883567, global = 2227.205, cumulative = 2230.435smoothSolver: Solving for epsilon, Initial residual = 0.08647006, Final residual = 0.000113174, No Iterations 1smoothSolver: Solving for k, Initial residual = 0.1579946, Final residual = 0.01115579, No Iterations 2ExecutionTime = 9.56 s ClockTime = 10 sTime = 3smoothSolver: Solving for Ux, Initial residual = 0.8070853, Final residual = 0.07865708, No Iterations 3smoothSolver: Solving for Uy, Initial residual = 0.8145663, Final residual = 0.03882168, No Iterations 4smoothSolver: Solving for Uz, Initial residual = 0.5761609, Final residual = 0.0390739, No Iterations 4smoothSolver: Solving for T, Initial residual = 0.1644957, Final residual = 0.006771158, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.7802636, Final residual = 0.006709539, No Iterations 13DICPCG: Solving for p_rgh, Initial residual = 0.04575494, Final residual = 0.0004415382, No Iterations 130DICPCG: Solving for p_rgh, Initial residual = 0.005830491, Final residual = 5.648426e-05, No Iterations 78time step continuity errors : sum local = 6.68889e+12, global = -4.053656e+11, cumulative = -4.053656e+11smoothSolver: Solving for epsilon, Initial residual = 1, Final residual = 0.08337707, No Iterations 1smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.08762031, No Iterations 2ExecutionTime = 11.24 s ClockTime = 11 sTime = 4smoothSolver: Solving for Ux, Initial residual = 0.1870785, Final residual = 0.008250987, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.1039591, Final residual = 0.003633928, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.003344756, Final residual = 0.0001428352, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.0360337, Final residual = 0.0008781286, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.9999995, Final residual = 0.7505781, No Iterations 1001DICPCG: Solving for p_rgh, Initial residual = 2.097918e-11, Final residual = 2.097918e-11, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 2.097918e-11, Final residual = 2.097918e-11, No Iterations 0time step continuity errors : sum local = 9.100777e+16, global = -1.152626e+15, cumulative = -1.153031e+15smoothSolver: Solving for epsilon, Initial residual = 0.006323925, Final residual = 0.0002800085, No Iterations 1smoothSolver: Solving for k, Initial residual = 0.9999998, Final residual = 0.08579136, No Iterations 4ExecutionTime = 15.48 s ClockTime = 16 sTime = 5smoothSolver: Solving for Ux, Initial residual = 0.6268107, Final residual = 0.01889084, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.5691313, Final residual = 0.02593386, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.525286, Final residual = 0.01999095, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.1776883, Final residual = 0.004896742, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.8409992, Final residual = 0.008296552, No Iterations 25DICPCG: Solving for p_rgh, Initial residual = 8.57445e-13, Final residual = 8.57445e-13, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 8.57445e-13, Final residual = 8.57445e-13, No Iterations 0time step continuity errors : sum local = 3.230307e+23, global = -5.044393e+14, cumulative = -1.657471e+15smoothSolver: Solving for epsilon, Initial residual = 4.732135e-05, Final residual = 1.311093e-10, No Iterations 1bounding epsilon, min: -1.103807e+26 max: 1.972571e+51 average: 2.670218e+47smoothSolver: Solving for k, Initial residual = 0.04771126, Final residual = 0.002285774, No Iterations 2ExecutionTime = 16.44 s ClockTime = 17 sTime = 6smoothSolver: Solving for Ux, Initial residual = 0.9995642, Final residual = 0.04432588, No Iterations 4smoothSolver: Solving for Uy, Initial residual = 0.9996968, Final residual = 0.04761556, No Iterations 4smoothSolver: Solving for Uz, Initial residual = 0.9858131, Final residual = 0.06924769, No Iterations 3smoothSolver: Solving for T, Initial residual = 0.01200576, Final residual = 0.0002952721, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.9446084, Final residual = 0.005339222, No Iterations 6DICPCG: Solving for p_rgh, Initial residual = 0.08971123, Final residual = 0.0008218812, No Iterations 6DICPCG: Solving for p_rgh, Initial residual = 0.02323654, Final residual = 0.0002319251, No Iterations 193time step continuity errors : sum local = 4.926861e+44, global = -1.110593e+37, cumulative = -1.110593e+37smoothSolver: Solving for epsilon, Initial residual = 1, Final residual = 0.002671469, No Iterations 2bounding epsilon, min: -2.219668e+47 max: 1.75779e+78 average: 3.182358e+73smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.0501481, No Iterations 2bounding k, min: -3.660183e+25 max: 9.966186e+62 average: 8.53815e+58ExecutionTime = 18.1 s ClockTime = 18 sTime = 7smoothSolver: Solving for Ux, Initial residual = 8.069155e-09, Final residual = 8.069155e-09, No Iterations 0smoothSolver: Solving for Uy, Initial residual = 5.382338e-08, Final residual = 7.473481e-09, No Iterations 1smoothSolver: Solving for Uz, Initial residual = 2.092083e-08, Final residual = 2.077615e-09, No Iterations 1smoothSolver: Solving for T, Initial residual = 0.1619372, Final residual = 0.003564584, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 1, Final residual = 46631.37, No Iterations 1001DICPCG: Solving for p_rgh, Initial residual = 1.64537e-26, Final residual = 1.64537e-26, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 1.64537e-26, Final residual = 1.64537e-26, No Iterations 0time step continuity errors : sum local = 1.468529e+53, global = 5.868436e+40, cumulative = 5.867326e+40smoothSolver: Solving for epsilon, Initial residual = 0.07343377, Final residual = 2.828068e-19, No Iterations 1bounding epsilon, min: -2.257804e+66 max: 8.093947e+109 average: 1.184346e+105smoothSolver: Solving for k, Initial residual = 0.5212037, Final residual = 0.02939162, No Iterations 2ExecutionTime = 22.26 s ClockTime = 22 sTime = 8smoothSolver: Solving for Ux, Initial residual = 0.6924604, Final residual = 0.01784756, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.3637153, Final residual = 0.005737122, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.2793264, Final residual = 0.00626238, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.07790577, Final residual = 0.002676894, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.8911507, Final residual = 0.008688155, No Iterations 18DICPCG: Solving for p_rgh, Initial residual = 1.957294e-52, Final residual = 1.957294e-52, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 1.957294e-52, Final residual = 1.957294e-52, No Iterations 0time step continuity errors : sum local = 8.548233e+90, global = -3.056251e+75, cumulative = -3.056251e+75--------------------------------------------------------------------------mpirun noticed that process rank 1 with PID 2840 on node default exited on signal 8 (Floating point exception).--------------------------------------------------------------------------[1] #0 Foam::error:rintStack(Foam::Ostream&)[0] #0 Foam::error:rintStack(Foam::Ostream&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[0] #1 Foam::sigFpe::sigHandler(int) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[1] #1 Foam::sigFpe::sigHandler(int) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[0] #2 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[1] #2 ? in "/lib64/libc.so.6"[0] #3 Foam::multiply(Foam::Field<double>&, Foam::UList<double> const&, Foam::UList<double> const&) in "/lib64/libc.so.6"[1] #3 Foam::multiply(Foam::Field<double>&, Foam::UList<double> const&, Foam::UList<double> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[0] #4 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam:perator*<Foam::fvPatchField, Foam::volMesh>(Foam::tmp<Foam::GeometricField<doub le, Foam::fvPatchField, Foam::volMesh> > const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[1] #4 void Foam::multiply<Foam::fvPatchField, Foam::volMesh>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so"[1] #5 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam:perator*<Foam::fvPatchField, Foam::volMesh>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so"[1] #6 Foam::RASModels::RNGkEpsilon<Foam::IncompressibleT urbulenceModel<Foam::transportModel> >::correct() in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so"[1] #7 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/buoyantBoussinesqSimpleFoam"[1] #8 __libc_start_main in "/lib64/libc.so.6"[1] #9 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/buoyantBoussinesqSimpleFoam"[default:02840] *** Process received signal ***[default:02840] Signal: Floating point exception (8)[default:02840] Signal code: (-6)[default:02840] Failing at address: 0x1f400000b18[default:02840] [ 0] /lib64/libc.so.6(+0x32660)[0x7f516d4f4660][default:02840] [ 1] /lib64/libc.so.6(gsignal+0x35)[0x7f516d4f45e5][default:02840] [ 2] /lib64/libc.so.6(+0x32660)[0x7f516d4f4660][default:02840] [ 3] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so(_ZN4Foam8multiplyERNS_5FieldIdEERKN S_5UListIdEES6_+0xd5)[0x7f516e7bfd55][default:02840] [ 4] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so(_ZN4Foam8mult iplyINS_12fvPatchFieldENS_7volMeshEEEvRNS_14Geomet ricFieldIdT_T0_EERKS6_S9_+0x41)[0x7f5172705861][default:02840] [ 5] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so(_ZN4FoammlINS _12fvPatchFieldENS_7volMeshEEENS_3tmpINS_14Geometr icFieldIdT_T0_EEEERKS7_RKS8_+0x15b)[0x7f5172784afb][default:02840] [ 6] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so(_ZN4Foam9RASM odels11RNGkEpsilonINS_29IncompressibleTurbulenceMo delINS_14transportModelEEEE7correctEv+0x2d0)[0x7f51727d5ec0][default:02840] [ 7] buoyantBoussinesqSimpleFoam[0x481a7d][default:02840] [ 8] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f516d4e0d1d][default:02840] [ 9] buoyantBoussinesqSimpleFoam[0x42db51][default:02840] *** End of error message ***…
Added by Mark JIN at 7:28pm on May 24, 2017
Topic: Butterfly/Openfoam floating issue
---------------------------------------------------------------*\| ========= | || \\ / F ield | OpenFOAM: The Open Source CFD Toolbox || \\ / O peration | Version: v1612+ || \\ / A nd | Web: www.OpenFOAM.com || \\/ M anipulation | |\*---------------------------------------------------------------------------*/Build : v1612+Exec : buoyantBoussinesqSimpleFoam -parallelDate : May 22 2017Time : 10:18:58Host : "default"PID : 2839Case : /home/ofuser/workingDir/butterfly/simple_hvacnProcs : 4Slaves : 3("default.2840""default.2841""default.2842")Pstream initialized with:floatTransfer : 0nProcsSimpleSum : 0commsType : nonBlockingpolling iterations : 0sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 10)allowSystemOperations : Allowing user-supplied system call operations// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //Create timeCreate mesh for time = 0SIMPLE: convergence criteriafield nut tolerance 0.0001field p_rgh tolerance 0.0001field k tolerance 0.0001field U tolerance 0.0001field T tolerance 0.0001field epsilon tolerance 0.0001field alphat tolerance 0.0001Reading thermophysical propertiesReading field TReading field p_rghReading field UReading/calculating face flux field phiSelecting incompressible transport model NewtonianCreating turbulence modelSelecting turbulence model type RASSelecting RAS turbulence model RNGkEpsilonRNGkEpsilonCoeffs{Cmu 0.0845;C1 1.42;C2 1.68;C3 -0.33;sigmak 0.71942;sigmaEps 0.71942;eta0 4.38;beta 0.012;}Reading field alphatReading gReading hRefCalculating field g.hNo MRF models presentRadiation model not active: radiationProperties not foundSelecting radiationModel noneNo finite volume options presentStarting time loopTime = 1smoothSolver: Solving for Ux, Initial residual = 1, Final residual = 0.06427477, No Iterations 4smoothSolver: Solving for Uy, Initial residual = 1, Final residual = 0.06226344, No Iterations 4smoothSolver: Solving for Uz, Initial residual = 1, Final residual = 0.03950103, No Iterations 3smoothSolver: Solving for T, Initial residual = 1, Final residual = 0.03671111, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 1, Final residual = 0.008356878, No Iterations 86DICPCG: Solving for p_rgh, Initial residual = 0.07888434, Final residual = 0.0006831407, No Iterations 9DICPCG: Solving for p_rgh, Initial residual = 0.007053905, Final residual = 6.211827e-05, No Iterations 71time step continuity errors : sum local = 3777.266, global = 3.22967, cumulative = 3.22967smoothSolver: Solving for epsilon, Initial residual = 0.9994728, Final residual = 0.0532353, No Iterations 4smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.05640973, No Iterations 4ExecutionTime = 2.65 s ClockTime = 3 sTime = 2smoothSolver: Solving for Ux, Initial residual = 0.5142984, Final residual = 0.02186577, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.5242573, Final residual = 0.02244622, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.5106874, Final residual = 0.02933279, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.3832824, Final residual = 0.01046751, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.9825413, Final residual = 0.009757923, No Iterations 799DICPCG: Solving for p_rgh, Initial residual = 0.04390194, Final residual = 0.000303611, No Iterations 9DICPCG: Solving for p_rgh, Initial residual = 0.0073043, Final residual = 7.259574e-05, No Iterations 45time step continuity errors : sum local = 1883567, global = 2227.205, cumulative = 2230.435smoothSolver: Solving for epsilon, Initial residual = 0.08647006, Final residual = 0.000113174, No Iterations 1smoothSolver: Solving for k, Initial residual = 0.1579946, Final residual = 0.01115579, No Iterations 2ExecutionTime = 9.56 s ClockTime = 10 sTime = 3smoothSolver: Solving for Ux, Initial residual = 0.8070853, Final residual = 0.07865708, No Iterations 3smoothSolver: Solving for Uy, Initial residual = 0.8145663, Final residual = 0.03882168, No Iterations 4smoothSolver: Solving for Uz, Initial residual = 0.5761609, Final residual = 0.0390739, No Iterations 4smoothSolver: Solving for T, Initial residual = 0.1644957, Final residual = 0.006771158, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.7802636, Final residual = 0.006709539, No Iterations 13DICPCG: Solving for p_rgh, Initial residual = 0.04575494, Final residual = 0.0004415382, No Iterations 130DICPCG: Solving for p_rgh, Initial residual = 0.005830491, Final residual = 5.648426e-05, No Iterations 78time step continuity errors : sum local = 6.68889e+12, global = -4.053656e+11, cumulative = -4.053656e+11smoothSolver: Solving for epsilon, Initial residual = 1, Final residual = 0.08337707, No Iterations 1smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.08762031, No Iterations 2ExecutionTime = 11.24 s ClockTime = 11 sTime = 4smoothSolver: Solving for Ux, Initial residual = 0.1870785, Final residual = 0.008250987, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.1039591, Final residual = 0.003633928, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.003344756, Final residual = 0.0001428352, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.0360337, Final residual = 0.0008781286, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.9999995, Final residual = 0.7505781, No Iterations 1001DICPCG: Solving for p_rgh, Initial residual = 2.097918e-11, Final residual = 2.097918e-11, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 2.097918e-11, Final residual = 2.097918e-11, No Iterations 0time step continuity errors : sum local = 9.100777e+16, global = -1.152626e+15, cumulative = -1.153031e+15smoothSolver: Solving for epsilon, Initial residual = 0.006323925, Final residual = 0.0002800085, No Iterations 1smoothSolver: Solving for k, Initial residual = 0.9999998, Final residual = 0.08579136, No Iterations 4ExecutionTime = 15.48 s ClockTime = 16 sTime = 5smoothSolver: Solving for Ux, Initial residual = 0.6268107, Final residual = 0.01889084, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.5691313, Final residual = 0.02593386, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.525286, Final residual = 0.01999095, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.1776883, Final residual = 0.004896742, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.8409992, Final residual = 0.008296552, No Iterations 25DICPCG: Solving for p_rgh, Initial residual = 8.57445e-13, Final residual = 8.57445e-13, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 8.57445e-13, Final residual = 8.57445e-13, No Iterations 0time step continuity errors : sum local = 3.230307e+23, global = -5.044393e+14, cumulative = -1.657471e+15smoothSolver: Solving for epsilon, Initial residual = 4.732135e-05, Final residual = 1.311093e-10, No Iterations 1bounding epsilon, min: -1.103807e+26 max: 1.972571e+51 average: 2.670218e+47smoothSolver: Solving for k, Initial residual = 0.04771126, Final residual = 0.002285774, No Iterations 2ExecutionTime = 16.44 s ClockTime = 17 sTime = 6smoothSolver: Solving for Ux, Initial residual = 0.9995642, Final residual = 0.04432588, No Iterations 4smoothSolver: Solving for Uy, Initial residual = 0.9996968, Final residual = 0.04761556, No Iterations 4smoothSolver: Solving for Uz, Initial residual = 0.9858131, Final residual = 0.06924769, No Iterations 3smoothSolver: Solving for T, Initial residual = 0.01200576, Final residual = 0.0002952721, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.9446084, Final residual = 0.005339222, No Iterations 6DICPCG: Solving for p_rgh, Initial residual = 0.08971123, Final residual = 0.0008218812, No Iterations 6DICPCG: Solving for p_rgh, Initial residual = 0.02323654, Final residual = 0.0002319251, No Iterations 193time step continuity errors : sum local = 4.926861e+44, global = -1.110593e+37, cumulative = -1.110593e+37smoothSolver: Solving for epsilon, Initial residual = 1, Final residual = 0.002671469, No Iterations 2bounding epsilon, min: -2.219668e+47 max: 1.75779e+78 average: 3.182358e+73smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.0501481, No Iterations 2bounding k, min: -3.660183e+25 max: 9.966186e+62 average: 8.53815e+58ExecutionTime = 18.1 s ClockTime = 18 sTime = 7smoothSolver: Solving for Ux, Initial residual = 8.069155e-09, Final residual = 8.069155e-09, No Iterations 0smoothSolver: Solving for Uy, Initial residual = 5.382338e-08, Final residual = 7.473481e-09, No Iterations 1smoothSolver: Solving for Uz, Initial residual = 2.092083e-08, Final residual = 2.077615e-09, No Iterations 1smoothSolver: Solving for T, Initial residual = 0.1619372, Final residual = 0.003564584, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 1, Final residual = 46631.37, No Iterations 1001DICPCG: Solving for p_rgh, Initial residual = 1.64537e-26, Final residual = 1.64537e-26, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 1.64537e-26, Final residual = 1.64537e-26, No Iterations 0time step continuity errors : sum local = 1.468529e+53, global = 5.868436e+40, cumulative = 5.867326e+40smoothSolver: Solving for epsilon, Initial residual = 0.07343377, Final residual = 2.828068e-19, No Iterations 1bounding epsilon, min: -2.257804e+66 max: 8.093947e+109 average: 1.184346e+105smoothSolver: Solving for k, Initial residual = 0.5212037, Final residual = 0.02939162, No Iterations 2ExecutionTime = 22.26 s ClockTime = 22 sTime = 8smoothSolver: Solving for Ux, Initial residual = 0.6924604, Final residual = 0.01784756, No Iterations 2smoothSolver: Solving for Uy, Initial residual = 0.3637153, Final residual = 0.005737122, No Iterations 2smoothSolver: Solving for Uz, Initial residual = 0.2793264, Final residual = 0.00626238, No Iterations 2smoothSolver: Solving for T, Initial residual = 0.07790577, Final residual = 0.002676894, No Iterations 2DICPCG: Solving for p_rgh, Initial residual = 0.8911507, Final residual = 0.008688155, No Iterations 18DICPCG: Solving for p_rgh, Initial residual = 1.957294e-52, Final residual = 1.957294e-52, No Iterations 0DICPCG: Solving for p_rgh, Initial residual = 1.957294e-52, Final residual = 1.957294e-52, No Iterations 0time step continuity errors : sum local = 8.548233e+90, global = -3.056251e+75, cumulative = -3.056251e+75--------------------------------------------------------------------------mpirun noticed that process rank 1 with PID 2840 on node default exited on signal 8 (Floating point exception).--------------------------------------------------------------------------[1] #0 Foam::error:rintStack(Foam::Ostream&)[0] #0 Foam::error:rintStack(Foam::Ostream&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[0] #1 Foam::sigFpe::sigHandler(int) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[1] #1 Foam::sigFpe::sigHandler(int) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[0] #2 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[1] #2 ? in "/lib64/libc.so.6"[0] #3 Foam::multiply(Foam::Field<double>&, Foam::UList<double> const&, Foam::UList<double> const&) in "/lib64/libc.so.6"[1] #3 Foam::multiply(Foam::Field<double>&, Foam::UList<double> const&, Foam::UList<double> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[0] #4 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam:perator*<Foam::fvPatchField, Foam::volMesh>(Foam::tmp<Foam::GeometricField<doub le, Foam::fvPatchField, Foam::volMesh> > const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so"[1] #4 void Foam::multiply<Foam::fvPatchField, Foam::volMesh>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so"[1] #5 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam:perator*<Foam::fvPatchField, Foam::volMesh>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so"[1] #6 Foam::RASModels::RNGkEpsilon<Foam::IncompressibleT urbulenceModel<Foam::transportModel> >::correct() in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so"[1] #7 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/buoyantBoussinesqSimpleFoam"[1] #8 __libc_start_main in "/lib64/libc.so.6"[1] #9 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/buoyantBoussinesqSimpleFoam"[default:02840] *** Process received signal ***[default:02840] Signal: Floating point exception (8)[default:02840] Signal code: (-6)[default:02840] Failing at address: 0x1f400000b18[default:02840] [ 0] /lib64/libc.so.6(+0x32660)[0x7f516d4f4660][default:02840] [ 1] /lib64/libc.so.6(gsignal+0x35)[0x7f516d4f45e5][default:02840] [ 2] /lib64/libc.so.6(+0x32660)[0x7f516d4f4660][default:02840] [ 3] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so(_ZN4Foam8multiplyERNS_5FieldIdEERKN S_5UListIdEES6_+0xd5)[0x7f516e7bfd55][default:02840] [ 4] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so(_ZN4Foam8mult iplyINS_12fvPatchFieldENS_7volMeshEEEvRNS_14Geomet ricFieldIdT_T0_EERKS6_S9_+0x41)[0x7f5172705861][default:02840] [ 5] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so(_ZN4FoammlINS _12fvPatchFieldENS_7volMeshEEENS_3tmpINS_14Geometr icFieldIdT_T0_EEEERKS7_RKS8_+0x15b)[0x7f5172784afb][default:02840] [ 6] /opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libincompressibleTurbulenceModels.so(_ZN4Foam9RASM odels11RNGkEpsilonINS_29IncompressibleTurbulenceMo delINS_14transportModelEEEE7correctEv+0x2d0)[0x7f51727d5ec0][default:02840] [ 7] buoyantBoussinesqSimpleFoam[0x481a7d][default:02840] [ 8] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f516d4e0d1d][default:02840] [ 9] buoyantBoussinesqSimpleFoam[0x42db51][default:02840] *** End of error message ***…
Added by Mark JIN to Ladybug Tools at 1:51am on May 31, 2017
Topic: Release Notes - November 9th 2015 - Ladybug 0.0.61 and Honeybee 0.0.58
tal at food4Rhino: http://www.food4rhino.com/project/ladybug-Honeybee?ufh Before addressing the changes in the software itself, we would like to announce the start of two new resources that have been added to help everyone learn and share knowledge across our community.   NEW RESOURCES GH Example File Sharing - After recognizing how important example files are for sharing knowledge and capabilities in our community, we have initiated a github-based platform for sharing Grasshopper definitions called Hydra:https://hydrashare.github.io/hydra/index.htmlWhile the database of files is a little over 50 files at the moment, it is hoped that this will become THE forum where much of collective knowledge is exchanged and shared into the future.  As you can see by clicking on any of the examples, you now are able to get a high-res visual of both the Rhino scene and the GH canvas without having to download files to your machine.  Furthermore the search functionality through the database enables you to quickly and easily see all that our community has contributed on certain subjects (just by searching “shade” or “wind” for example).In addition to other files that have been contributed, you can find all of the original Ladybug examples here:https://hydrashare.github.io/hydra/index.html?keywords=LBExampleFilesAnd all of the original Honeybee examples here:https://hydrashare.github.io/hydra/index.html?keywords=HBExampleFiles LB+HB Documentation - While our historical practice of including all documentation within component descriptions may have sufficed up until this point, we have since recognized that an online database of all this documentation would be helpful.  Now, you can search for key terms throughout the entire documentation of the project in our beautiful online documentation database created by Mostapha:https://www.gitbook.com/book/mostapharoudsari/ladybug-primer/detailshttps://www.gitbook.com/book/mostapharoudsari/honeybee-primer/details And now, onto the major changes and enhancements in the software:   LADYBUG Photovoltaics Components - Based on original code from NREL’s PVWatts (http://pvwatts.nrel.gov), Djordje Spasic and Jason Sensibaugh have built a set of 5 components that perform detailed estimate of the electricity generated by Rhino/Grasshopper surfaces when populated with Photovoltaics (PV) modules.Components allow definition of losses and shading, finding optimal tilt and orientation angles, analysing performance, energy value, consumption and emissions of the PV system. Enhanced Solar Envelope - Boris Plotnikov has contributed a solar envelope component that is not only much faster and more stable than the previous component but also allows you to input the geometries of buildings for which you would like to ensure solar access.  This enables customization of the solar envelope to specific urban contexts in a manner that the previous envelope did not.  The component also features a “solar access” option that draws the envelope above which a given site receives sun from a set of sun vectors. An example file can be found here:http://hydrashare.github.io/hydra/viewer?owner=boris-p&fork=hydra&id=SolarEnvelope Adaptive Comfort Chart - To assist with understanding the variations of the adaptive comfort model, an Adaptive Comfort Chart component has been added that functions in a similar manner to the psychrometric chart for the PMV model.  In addition to granting a visualization of the adaptive standard itself, the chart is also particularly helpful for displaying the results of energy simulations in relation to the comfort polygon.  The chart is based off of the UC Berkeley Center for the Built Environment’s Comfort Tool (http://comfort.cbe.berkeley.edu/) (https://github.com/CenterForTheBuiltEnvironment/comfort_tool).  An example file can be found here:http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Adaptive_Comfort_Chart Full Support for US + European Thermal Comfort Standards - Ladybug now supports the ability to model any of the variations of the Adaptive/PMV models for both the US (ASHRAE) and European (ISO) standards.  This includes varying thresholds of percentage of people dissatisfied (PPD), varying thresholds for humidity ratios, the ability to use either a monthly average or daily running mean temperatures in the adaptive model, and even some functions that are not yet a part of these standards but are referenced widely in thermal comfort research.  Such widely referenced functions include the ability to apply the adaptive model’s method to conditioned or mixed-mode buildings as well as the application of the adaptive model to times of the year when it is considered too cold by ASHRAE and the ISO for an adaptive standard.  All of these variations on the standards can be accessed through the new “PMV Comfort Parameters” and “Adaptive Comfort Parameters” components.  As a final nod to dual support for US/European standards, it is now possible to view the psychrometric chart as a Molier i,x diagram. EPWMap - After years of struggling with the text-based indexing of the DOE’s epw file database, it is now possible to search for weather files using a map interface and search bar thanks to Mostapha’s recent web interface built with D3 and GoogleMaps (http://mostapharoudsari.github.io/epwmap/).  From here on out, the Ladybug “Download EPW” component will direct you to this interface. “RunItAll” Released as “Fly” - In preparation for future features that will assist with exploring of large multidimensional design spaces, this release of Ladybug includes a component by the name of “Fly” that is meant to run through all of the combinations of a given set of sliders.  Those who follow this forum closely might recognize it as a reincarnated version of a component called “RunItAll” that appeared in some older example files. You can find an example file here: http://hydrashare.github.io/hydra/viewer?owner=mostaphaRoudsari&fork=hydra_1&id=Parametric_Daylight_Analysis Shade Benefit Evaluator Validated + Published - After a long process of testing, the key functions within the comfort and energy shade benefit evaluator components have been validated against several similar software and energy modeling tools.  A paper published to the SimAUD conference regarding this validation can be found here: https://www.dropbox.com/s/tvdj6d2giswurew/SIMAUD_Paper12.pdf?dl=0.  Special recognition goes to Panagiotis Samaras, who ran many of these intensive tests for his thesis.  Along with this validation, there are a few more variables that have been exposed to allow more freedom of running the shade benefit functions including the use of higher sky resolutions and multiple shade benefit test regions for a given shade. Color Gradient Library - After realizing that several of us wanted quick access to common color gradients that we frequently plug into the Legend Parameters component, we have now added a component called “Color Gradient Library” to do just this.  An image displaying all of these gradients can be found here:https://github.com/mostaphaRoudsari/ladybug/blob/master/resources/gradients.jpgAnd an example file showing how to use the library can be found here:http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Color_LibraryIf you feel that there is a common gradient that is currently missing, feel free to start a discussion on our GH group about it and we should include it soon. Solar Time Available - The Ladybug Sunpath now includes an option to display solar time, which many have found to be more intuitive and easy to work with when designing with solar geometry.  Solar time is also useful for minimizing an east vs west bias that can develop in sunlight hour studies without having to generate sun vectors at very small timesteps. Monthly/Daily Totals for Hourly Data - The Ladybug “Average Data” component now includes the ability to total the values for months and days (as opposed to timply averaging them).  This is useful particularly when you want to get monthly or daily values of total energy or visualize these totals on the monthly bar chart. Increased IP Functionality - This release of Ladybug includes several more features that assist with converting data for an IP audience including the ability to view an IP Psychrometric or Adaptive Chart by plugging in temperature values in Farenheit as well as a number of and new converter components for the following: Wh to BTU, R-Value SI to R-Value IP, m/s to mph, Liters to Gallons.  Note that Honeybee is still largely SI (requiring your Rhino model to be in meters to run energy simulations). Mesh-to-Hatch and Future BakeIt Plans - Given that the current BakeIt_ option has only been implemented on a few components with relatively minimal use, it has been decided that future implementations of BakeIt_ will provide not just a means of recording parametric results in the Rhino scene but will also support a full pathway to vector-based programs (like Illustrator and Inkscape).  As such, BakeIt_ will place text in the Rhino scene as actual editable text (not meshes) and colored meshes will be output as groups of colored hatches (so that they appear as color-filled polygons in vector-based programs).  In order to give those interested in this future capability a chance to experiment at the present, a “Mesh-To-Hatch” component has been added to the Extra tab. HONEYBEE Fully Functional Microclimate Maps - Finally, after a long and arduous thesis followed by a couple of months of bug-fixing, Chris Mackey is pleased to announce that the ability to produce high resolution temperature maps from EnergyPlus results is complete.  Together, these maps account for four key variables that produce microclimatic diversity in and around buildings - MRT variation from different surface temperatures, solar radiation shining directly on occupants, average air temperature diversity, and air temperature stratification.  In addition to using these 4 variables to produce high-resolution visuals of temperature, it is also possible to produce maps of thermal comfort by using any of the three primary thermal comfort models in Ladybug (PMV, Adaptive, and Outdoor (UTCI)).  Support currently exists to produce maps for both indoor and outdoor conditions and, while the temperature values and indoor comfort values currently produced are highly accurate, the outdoor wind speeds are calculated using the simplified assumptions of EnergyPlus and will be revised to enable more accurate accounting for the effects of wind on outdoor comfort in the next stable release. The whole workflow is broken down into eight components that can all be found under the 9 | Energy Energy tab. For some videos showing some time-lapse thermal renderings made from these tools see this video playlist:https://www.youtube.com/playlist?list=PLruLh1AdY-Sj3ehUTSfKa1IHPSiuJU52AFor the full 150-page documentation of the tools produced for Chris’s thesis, see this link:https://www.dropbox.com/s/k4r4rd279y4td9n/Mackey_Thesis.pdf?dl=0Finally, if you want to dive in and produce some comfort maps for yourself, you can find an example file here for indoor maps:http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Indoor_Microclimate_MapAnd an example file here for outdoor maps:http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Outdoor_Microclimate_Map Thermal Autonomy / Thermal Comfort Percent - In addition to the new thermal mapping capabilities, this release includes the ability to use these maps to calculate a series of spatial thermal comfort metrics that are meant to mirror the metrics currently used to evaluate daylight (daylight autonomy, UDI, etc.).  Specifically, these metrics are the following:Thermal Comfort Percent - The percentage of occupied time that a given point in space is thermally comfortable.Thermal Autonomy - The percentage of occupied time that a given point in space is thermally comfortable without the addition of any heating or cooling energy.Overheated Hours - The percentage of occupied time when a given point is space is too hot to be thermally comfortable.Underheated Hours - The percentage of occupied time when a given point is space is too cold to be thermally comfortable.All of these metrics can be accessed through the “Thermal Autonomy Analysis” component and you can find an example file here:http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Comfort_Autonomy Energy Balance Visualizations - In order to help understand the flow of energy through Honeybee energy models, it is now possible to completely reconstruct the energy balance calculation of EnergyPlus from the energy simulation results.  This is facilitated by the new EnergyPlus “Construct Energy Balance” component and some new features added to the monthly bar chart.  See here for an example:http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Energy_Balance More Geometry Control for Glazing - In order to make it faster to assign several different types of glazing geometries to your energy models, the “AddHBGlz” can now be used to add glazing surfaces to HBzones (not just HBsurfaces).  Furthermore, the “Glazing Based on Ratio” component now contains several more inputs that enable you to customize window geometry on orthogonal surfaces, including the ability to set the horizontal distance between windows and the ability to split windows vertically into a lower view window and higher daylight window. Earth Tube Capability - Thanks to the efforts of Anton Szilasi, it is now possible to assign earth tubes to your energy models in order to test the potential of this powerful passive strategy.  See here for an example file:http://hydrashare.github.io/hydra/viewer?owner=antonszilasi&fork=hydra&id=HB_EarthTube North Input For Annual Daylight - After the toil of having to rotate your model any time you wanted to run an annual daylight analysis, we are happy to announce that the annual daylight recipe now contains a working “North” input. Honeybee Object Transforms - After realizing that many of us wanted to construct energy models of multi-story buildings by duplicating and moving zones, this capability is now easily facilitated with a set of three components to duplicate and transform your HBObjects.  Specifically, this includes a component to move (translate) your HBObject, mirror (reflect) your HBObject, and rotate your HBObject.  Using these components ensures that any properties that you have assigned to your original HBObject will be present in the transformed HBOjbect, allowing you to build large energy models very quickly. The three components can currently be found under the WIP tab.   And finally, it is with great pleasure that we welcome Boris Plotnikov to the team. As mentioned in the above release notes, Boris has added a highly advanced solar envelope component to the project.   As always let us know your comments and suggestions.   Enjoy! Ladybug+Honeybee development team  …
Added by Chris Mackey to Ladybug Tools at 2:12am on November 9, 2015
Comment on: Topic 'exporting mesh from rhino to fea'
ttern with many panels is an assembly. an assembly is made of parts. The cardinal thing is that Rhino does not export a mesh in these formats but only surfaces or solids..and then one must remesh them in Abaqus.. I'm trying to export the mesh itself. here are the supported file formats as Abaqus describes them: Abaqus/CAE reads and writes geometry data stored in the following formats: 3D XML (file_name.3dxml) 3D XML is an XML-based format developed by Dassault Systèmes for encoding three-dimensional images and data. The format is open and extendable, allowing three-dimensional graphics to be easily shared and integrated into existing applications and processes. 3D XML files can be many times smaller than typical model database files. The 3D XML Player from Dassault Systèmes is required to view 3D XML files or to integrate them into business applications. You can also view 3D XML files in CATIA V5. You can export viewport data from Abaqus/CAE in 3D XML or compressed 3D XML format. For more information, see “Exporting viewport data to a 3D XML-format file,” Section 10.9.5. You cannot import 3D XML into Abaqus/CAE. Abaqus/Standard and Abaqus/Explicit input files Abaqus/CAE generates an input file when you submit a job for analysis. You can import input files into Abaqus/CAE. Abaqus/CAE translates the keywords and data lines in the imported input file into a new model; however, a limited set of Abaqus/Standard and Abaqus/Explicit keywords is supported, as described in “Importing a model from an Abaqus/Standard or an Abaqus/Explicit input file,” Section 10.5.1. For more information on creating and submitting jobs, see “Basic steps for analyzing a model,” Section 18.2.1. ACIS (file_name.sat) ACIS is a library of solid modeling functions developed by Spatial, and most CAD products can generate ACIS-format parts. You can import ACIS-format parts, and you can export parts or the assembly in ACIS format. In addition, you can import and export sketches in ACIS format. For more information, see “Importing parts from an ACIS-format file,” Section 10.7.4; “Importing sketches,” Section 10.7.1; and “Exporting geometry and model data,” Section 10.9. AutoCAD (file_name.dxf) Two-dimensional profiles stored in AutoCAD (.dxf) files can be imported as stand-alone sketches. However, Abaqus/CAE supports only a limited number of AutoCAD entities, and you should use this format only if no other formats are available. For more information and details on the AutoCAD entities supported by Abaqus/CAE, see “Importing sketches,” Section 10.7.1. CATIA V4 (file_name.model, file_name.catdata, or file_name.exp) CATIA is a CAD/CAM/CAE software package marketed by IBM and Dassault Systèmes. You can import CATIA-format parts. You can also import an entire CATIA V4 assembly into the Abaqus/CAE assembly, or you can choose to import only selected part instances. For more information, see “Importing a part from a CATIA V4- or V5-format file,” Section 10.7.5; and “Importing an assembly from a CATIA V4-format file,” Section 10.7.13. You cannot export parts from Abaqus/CAE in CATIA format. CATIA V5 Elysium Neutral File or Elysium Neutral Assembly File (file_name.enf_abq or .eaf_abq) A translator plug-in is available for CATIA V5 that will generate a geometry file using the Elysium Neutral File (.enf) format or the Elysium Neutral Assembly File (.eaf) format. You can use Elysium Neutral Files to import CATIA V5 parts. In addition, you can use Elysium Neutral Files or Elysium Neutral Assembly Files to import an entire CATIA V5 assembly into the Abaqus/CAE assembly, or you can choose to import only selected part instances. For more information, see “Importing a part from an Elysium Neutral file,” Section 10.7.6, and “Importing an assembly from an Elysium Neutral file,” Section 10.7.14. You cannot export parts or assemblies from Abaqus/CAE in Elysium Neutral File or Elysium Neutral Assembly File format. CATIA V5 parts and assemblies (file_name.CATPart or .CATProduct) With the optional CATIA V5 Associative Interface add-on feature for Abaqus/CAE, you can import CATIA V5-format parts and assemblies. For more information, see “Importing a part from a CATIA V4- or V5-format file,” Section 10.7.5. You cannot export parts from Abaqus/CAE in CATIA V5 format. I-DEAS Elysium Neutral File or Elysium Neutral Assembly File (file_name.enf_abq or .eaf_abq) Abaqus provides a translator plug-in for I-DEAS that will generate a geometry file using the Elysium Neutral File (.enf) format or the Elysium Neutral Assembly File (.eaf) format. You can use Elysium Neutral Files to import I-DEAS parts. In addition, you can use Elysium Neutral Files or Elysium Neutral Assembly Files to import an entire I-DEAS assembly into the Abaqus/CAE assembly, or you can choose to import only selected part instances. For more information, see “Importing a part from an Elysium Neutral file,” Section 10.7.6, and “Importing an assembly from an Elysium Neutral file,” Section 10.7.14. You cannot export parts or assemblies from Abaqus/CAE in Elysium Neutral File or Elysium Neutral Assembly File format. IGES (file_name.igs or .iges) The Initial Graphics Exchange Specification (IGES) is a neutral data format designed for graphics exchange between computer-aided design (CAD) systems. You can import IGES-format parts, and you can export parts in IGES format. In addition, you can import and export sketches in IGES format. For more information, see “Importing a part from an IGES-format file,” Section 10.7.7;“Importing sketches,” Section 10.7.1; and “Exporting geometry and model data,” Section 10.9. The IGES-format allows for many interpretations, and most of the parts that you import into Abaqus/CAE using IGES-format will need to be repaired before you can use them. Thus, it is recommended that you try to use another format, if possible. Output database (output_database_ name.odb) An output database contains the data generated during an Abaqus/Standard or Abaqus/Explicit analysis. You can import parts from an output database in the form of orphan meshes. An orphan mesh part contains no feature information and is extracted from the output database as a collection of nodes, elements, surfaces, and sets. If the output database contains multiple part instances, you can select the part instances to import. Abaqus/CAE imports each part instance as a separate orphan mesh part. You can import either the undeformed or the deformed shape. If you import the deformed shape, you can specify the step and the frame from which to import. To verify the quality of the orphan mesh, you can display the orphan mesh part in the Mesh module and select MeshVerify from the main menu bar. In addition, you can use the Mesh module to change the element type assigned to the mesh and to edit the original mesh definition. For more information, see “Importing a part from an output database,” Section 10.7.12; “What can I do with the Edit Mesh toolset?,” Section 46.1; and “Assigning Abaqus element types,” Section 17.5. You can also import a model from an output database. The model that is imported will contain orphan mesh parts representing each of the undeformed part instances in the output database along with an orphan mesh representation of the undeformed assembly. The model will also contain any sets, surfaces, materials, section definitions, and beam profiles that were defined in the output database. For more information, see “Importing a model from an output database,” Section 10.5.2. Parasolid (file_name.x_t, file_name.x_b, file_name.xmt_txt, or file_name.xmt_bin) Parasolid is a library of solid modeling functions developed by UGS. A variety of CAD products can generate Parasolid-format parts, such as NX, SolidWorks, Solid Edge, FEMAP, and MSC.Patran. You can import Parasolid-format parts. You can also import an entire Parasolid assembly into the Abaqus/CAE assembly, or you can choose to import only selected part instances. For more information, see “Importing a part from a Parasolid-format file,” Section 10.7.9; and “Importing an assembly from a Parasolid-format file,” Section 10.7.15. You cannot export parts or assemblies from Abaqus/CAE in Parasolid format. Pro/ENGINEER Elysium Neutral File or Elysium Neutral Assembly File (file_name.enf_abq or .eaf_abq) Abaqus provides a translator plug-in for Pro/ENGINEER that will generate a geometry file using the Elysium Neutral File (.enf) format or the Elysium Neutral Assembly File (.eaf) format. You can use Elysium Neutral Files to import Pro/ENGINEER parts. In addition, you can use Elysium Neutral Files or Elysium Neutral Assembly Files to import an entire Pro/ENGINEER assembly into the Abaqus/CAE assembly, or you can choose to import only selected part instances from the assembly. For more information, see “Importing a part from an Elysium Neutral file,” Section 10.7.6, and “Importing an assembly from an Elysium Neutral file,” Section 10.7.14. You cannot export parts or assemblies from Abaqus/CAE in Elysium Neutral File or Elysium Neutral Assembly File format. STEP (file_name.stp or .step) The STandard for the Exchange of Product model data (STEP ISO 10303–1) is designed as a high-level replacement for IGES that attempts to overcome some of the shortcomings of IGES. The STEP AP203 standard is designed to provide a computer-interpretable representation of a mechanical product throughout its life cycle, independent of any particular system. You can import STEP-format parts, and you can export parts in STEP format. In addition, you can import and export sketches in STEP format. For more information, see “Importing a part from a STEP-format file,” Section 10.7.10; and“Exporting geometry and model data,” Section 10.9. STEP-format parts are similar to IGES-format parts in that most of the parts that you import into Abaqus/CAE using STEP-format will need to be repaired before you can use them. Thus, it is recommended that you try to use another format, if possible. VDA-FS (file_name.vda) The Verband der Automobilindustrie Flachën Schnittstelle (VDA-FS) surface data format is a geometry standard developed by the German automotive industry. Both VDA-FS and IGES files contain a mathematical representation of the part in an ASCII format; however, the VDA-FS standard concentrates on geometry information. Additional information covered by the IGES standard, such as dimensions, text, and colors, is not stored in a VDA-FS file. You can import VDA-FS-format parts, and you can export parts in VDA-FS format. For more information, see “Importing a part from a VDA-FS-format file,” Section 10.7.11; and “Exporting geometry and model data,” Section 10.9. VDA-FS format parts are similar to IGES-format parts in that most of the parts that you import into Abaqus/CAE using VDA-FS format will need to be repaired before you can use them. Thus, it is recommended that you try to use another format, if possible. VRML (file_name.wrl) Virtual Reality Modeling Language (VRML) is the ISO standard for displaying three-dimensional images in a web browser or a stand-alone VRML client. It is an open, platform-independent, vector-based, three-dimensional modeling language that encodes computer-generated graphics to allow them to be shared easily across a network. VRML-format files can be many times smaller than typical model database files. A special plug-in viewer, such as Cortona or Cosmo, is required to view VRML files. You can export viewport data from Abaqus/CAE in VRML format or compressed VRML format. For more information, see “Exporting viewport data to a VRML-format file,” Section 10.9.4. …
Added by kipodi at 11:09am on January 28, 2016
  • 1
  • ...
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212

About

Scott Davidson created this Ning Network.

Welcome to
Grasshopper

Sign In

Translate

Search

Photos

  • Circuit Pavilion Rhino Grasshopper Tutorial

    Circuit Pavilion Rhino Grasshopper Tutorial

    by June Lee 0 Comments 1 Like

  • Circuit Pavilion Rhino Grasshopper Tutorial

    Circuit Pavilion Rhino Grasshopper Tutorial

    by June Lee 0 Comments 0 Likes

  • Vase

    Vase

    by Andrey Zotov 0 Comments 2 Likes

  • Vase Mesh

    Vase Mesh

    by Andrey Zotov 0 Comments 1 Like

  • Patterns

    Patterns

    by Andrey Zotov 0 Comments 0 Likes

  • Add Photos
  • View All
  • Facebook

Videos

  • Circuit Pavilion Rhino Grasshopper Tutorial

    Circuit Pavilion Rhino Grasshopper Tutorial

    Added by June Lee 0 Comments 0 Likes

  • Floating Mobius Pavilion Rhino Grasshopper Tutorial

    Floating Mobius Pavilion Rhino Grasshopper Tutorial

    Added by June Lee 0 Comments 0 Likes

  • Magnet Shade Pavilion Rhino Grasshopper Tutorial

    Magnet Shade Pavilion Rhino Grasshopper Tutorial

    Added by June Lee 0 Comments 0 Likes

  • Ngon Mesh

    Ngon Mesh

    Added by Parametric House 1 Comment 0 Likes

  • Minimal Surface

    Minimal Surface

    Added by Parametric House 0 Comments 0 Likes

  • Wind Pavilion

    Wind Pavilion

    Added by Parametric House 0 Comments 0 Likes

  • Add Videos
  • View All
  • Facebook

© 2026   Created by Scott Davidson.   Powered by Website builder | Create website | Ning.com

Badges  |  Report an Issue  |  Terms of Service