mesa_script 0.1 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ca9b7036396472f5a9ea98119ef282a875bac4e8
-  data.tar.gz: 6e2c6f0ffa3ef59365fd03815ea81b88fa5b316c
+  metadata.gz: 55896301a082301610d80908f4c961af244e4a73
+  data.tar.gz: efd7bc215b3b3d2a856159695952c2e24654ea6f
 SHA512:
-  metadata.gz: 46b15cee048454f84c79bfc6deaafe9356b91cfd60959599b7d874ab3a80194118d88e19c91b0ce26e9084933c65f52f8f37624b0f56a2c40b9fab78c75c5f0e
-  data.tar.gz: 28b1bc30eec9a956f760b30fda344c54f869f266fc94cc305c5893ce704efe9d13c629ba32256730dcadd799966faff035250b3f0547880604d7bfc92a3c772f
+  metadata.gz: f279cea9e1082ef5b5066854e2377214e725a5cff6f53ede2802bbc3d4762875d4c5339d99054fde80c7b2690bda64e8cb596ad10aa12a64084ec5f29720c79c
+  data.tar.gz: 49da8ec75ef95dc5878f6cd8c9b42d6dfce1585a2761c32934e05c9a1224d92e35cadfb99b23330c9f56287f4d3b2d801d2c0d8a8425aee0e66c75757be2e2a7

data/README.md

@@ -44,9 +44,18 @@ set of parameters, run MESA star, then use the output of that run to dictate a
 new inlist and run, creating a chain (maybe a MESA root find of sorts).
 
 ###Installation
-Someday, I hope to package this as a gem, but for now, it's staying hosted on
-Github, which means you need to install it yourself. Clone or otherwise
-download the repository somewhere to your home directory with
+MesaScript is now available as a gem! Assuming you have the `gem` command up
+and running (you probably do, but if not, check out 
+[RubyGems](https://rubygems.org) to get it up and running). Simply run
+
+    gem install mesa_script
+
+and you should be good to go. You'll be able to include MesaScript in your
+ruby files with `require mesa_script`, and `inlist2mesascript` will be 
+available to you from the command line to convert your existing inlists to
+mesascript files.
+
+If you want to edit the source or don't want to use rubygems, clone or otherwise download the repository somewhere to your home directory with
 
     git clone https://github.com/wmwolf/MesaScript.git ~/MesaScript
 

data/lib/mesa_script.rb

@@ -68,7 +68,9 @@ class Inlist
   # Three ways to access array categories. All methods will cause the
   # data category to be staged into your inlist, even if you do not change it
   # Basically, if it appears in your mesascript, it will definitely appear
-  # in your inlist. There is no way to unflag an entry.
+  # in your inlist. A command can be unflagged by calling 
+  # `unflag_command('COMMAND_NAME')` where COMMAND_NAME is the case-sensitive
+  # name of the command to be unflagged.
   #
   # 1. Standard array way like
   #        xa_lower_limit_species[1] = 'h1'
@@ -165,7 +167,7 @@ class Inlist
   # Two ways to access/change scalars. All methods will cause the data category
   # to be staged into your inlist, even if you do not change the value.
   # Basically, if it appears in your mesascript, it will definitely appear in
-  # your inlist. There is no way to unflag an entry.
+  # your inlist. 
   #
   # 1. Change value, like
   #        initial_mass(1.0)
@@ -181,6 +183,10 @@ class Inlist
   #    syntaxes are allowed, though the one without parentheses is more
   #    traditional for ruby (why do you want empty parentheses anyway?). Returns
   #    current value.
+  #
+  # A command can be unflagged by calling `unflag_command('COMMAND_NAME')` 
+  # where COMMAND_NAME is the case-sensitive name of the command to be
+  # unflagged.
 
   def self.make_regular_method(datum)
     name = datum.name

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mesa_script
 version: !ruby/object:Gem::Version
-  version: '0.1'
+  version: 0.1.1
 platform: ruby
 authors:
 - William Wolf