You might try looking at this tutorial for some ideas.
Personal Database of Molecules
Cocoa for Scientists (Part XXII): Core Data Models
By drewmccormack at Mon, Feb 4 2008 9:04am
http://www.macresearch.org/cocoa-scientists-part-xxii-core-data-models
If you want specific recommendations from others you might need to
state your problem in more generic terms. Not everyone here is
familiar with material science.
Richard
On Jul 6, 2009, at 4:24 PM, Ben Guest wrote:
I am using Core Data to create a material database to be used for
tracking engineering materials. Each material has a bunch of
different material properties (modulus, poison's ratio, failure and
yield strength, ect). Depending on the type of material
(anisotropic, orthotropic, isotropic, composite, ect) the material
might have 1 of each of these properties (for an isotropic
material), or it might have up to 9 (for an orthotropic material). I
would also like to simplify my code, by say looping over a
particular properties (where appropriate).
The question is it better to store these properties as attributes of
a material managed object, for example for young's modulus
(modulus_1, modulus_2... ect) or is it better to create a
relationship-to-many that references a managed object that has
attributes of a value and number.
What would be ideal is a managed object that could manage arrays of
data as eventually these properties will have to be transferred to c
array style arrays for various calculations.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
