Most recent edit on 2008-05-09 13:28:04 by LoneGunman
Deletions:
Completed Employee Training as assigned by Rao:
Meetings:
Concerns: Need to schedule time with someone (Mark?) to go through Docato as far as how we use it, workflow, checkin policies, and so forth.
Edited on 2008-05-09 13:23:11 by LoneGunman
Additions:
Completed Employee Training as assigned by Rao:
Meetings:
Concerns: Need to schedule time with someone (Mark?) to go through Docato as far as how we use it, workflow, checkin policies, and so forth.
Edited on 2008-05-06 13:04:10 by LoneGunman
Deletions:
There are 2 main functions of the Stilo tool:
The attached files are the sequence of files generated by running Stilo's ruleset transform tool. BACB30NM is used as an example - see the attached PDF version for your reference. I will describe the 2 steps above in greater detail here.
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato.
2) Ruleset Transform - This will be a Docato publication that strips out the ruleset XML from the part standard, then converts back to the ruleset language; the resulting file must be sent to the BMTdev environment for testing & approval.
Edited on 2008-05-06 12:04:47 by LoneGunman
Additions:
- bacb30nm-ruleset.txt∞ is the current form of all existing rulesets - this is the file I started with. bacb30nm-ruleset-rs.xml∞ is the ruleset as converted to XML.
BACB30NM-merged.xml∞ is the ruleset XML merged into the part standard XML - this is the form that will reside in Docato as authoritative data. This completes step 1.
Deletions:
- bacb30nm-ruleset.txt∞ is the current form of all existing rulesets - this is the file I started with. bacb30nm-ruleset-rs.xml∞ is the ruleset as converted to XML.
BACB30NM-merged.xml∞ is the ruleset XML merged into the part standard XML - this is the form that will reside in Docato as authoritative data. This completes step 1.
Edited on 2008-05-06 12:01:12 by LoneGunman
Additions:
- Demo Documentation.doc Table Documentation.doc
The attached files are the sequence of files generated by running Stilo's ruleset transform tool. BACB30NM is used as an example - see the attached PDF version for your reference. I will describe the 2 steps above in greater detail here.
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato.
Deletions:
- Ruleset Demo Documentation.doc Dimension Table Documentation.doc
The attached files are the sequence of files generated by running Stilo's ruleset transform tool. BACB30NM is used as an example - see the attached PDF version for your reference. I will describe the 2 steps above in greater detail here.
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato. Mark should have ideas on how this should be set up to run Stilo's scripts.
Edited on 2008-05-06 11:17:08 by LoneGunman
Additions:
- Ruleset Demo Documentation.doc Dimension Table Documentation.doc
Deletions:
RulesetDemoDocumentation.doc DimensionTableDocumentation.doc
Edited on 2008-05-06 11:16:28 by LoneGunman
Additions:
DimensionTableDocumentation.doc
These are the documents Stilo provided with their Ruleset Transform and Tab File Transform Demo respectively. In testing the tools they provided, I have not found any major gaps in the Ruleset transform tools. From what I can see, they are fairly close to being production-ready. There are however, several large gaps in the Tab file transform. Stilo has provided us basically with a demo showing that they can do what we asked, but needs a lot more work to use in a production environment.
Edited on 2008-05-06 11:08:28 by LoneGunman
Additions:
There are 2 main functions of the Stilo tool:
The attached files are the sequence of files generated by running Stilo's ruleset transform tool. BACB30NM is used as an example - see the attached PDF version for your reference. I will describe the 2 steps above in greater detail here.
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato. Mark should have ideas on how this should be set up to run Stilo's scripts.
2) Ruleset Transform - This will be a Docato publication that strips out the ruleset XML from the part standard, then converts back to the ruleset language; the resulting file must be sent to the BMTdev environment for testing & approval. Collin Bennett & Greg Kahler should be able to tell you more about the BMTdev end of it.
Edited on 2007-11-18 17:43:48 by LoreWeaver
Additions:
where each can be a range between 1-254 and where $ip4 = 254 increment ip3 by 1
Deletions:
where each can be a range between 1-254 and where $ip4 = 254 increment ip3 by 1 () then run through the first loop again til 254, increment ip3 again, loop, etc.
Edited on 2007-11-18 17:42:11 by LoreWeaver
Additions:
Clear Wisdom is wisdom that discerns its object clearly and precisely. If we can understand with ease whatever we attempt to understand, if we have clear memory and imagination, and if we can distinguish the subtlest topics such as impermanence and emptiness, this indicates that we have clear wisdom. With clear wisdom we can clearly recall what has been understood. Clear wisdom brings clear concentration which we will need in order to progress on the path to preparation.
Edited on 2007-11-15 22:51:44 by LoreWeaver
Deletions:
Edited on 2007-10-22 13:29:08 by LoreWeaver
Additions:
Edited on 2006-05-09 20:25:32 by LoreWeaver
Additions:
Think of it this way. You have two variables:
$ip3 = 1;
$ip4 = 1;
where each can be a range between 1-254 and where $ip4 = 254 increment ip3 by 1 () then run through the first loop again til 254, increment ip3 again, loop, etc.
Edited on 2006-05-09 19:53:29 by LoreWeaver
Additions:
Looping: The + operator is overloaded to enable looping through a range.
Example:
Deletions:
Looping: The + operator is overloaded to enable looping through a range. Example:
Edited on 2006-05-09 19:53:13 by LoreWeaver
Additions:
Looping: The + operator is overloaded to enable looping through a range. Example:
Deletions:
Looping: The + operator is overloaded to enable looping through a range. Example: ($x)
Oldest known version of this page was edited on 2006-05-09 19:52:24 by LoreWeaver []
Looping: The + operator is overloaded to enable looping through a range. Example: ($x)
Deletions:
Michael Maloney's status for week of 5/5-9/2008
This week I have been getting up to speed on new hire activities, the project and development environment including:Completed Employee Training as assigned by Rao:
- TR011018 - Laptop Security Training
- TR005487 - Acceptance of Business Courtesies - Anti-Kickback
- TR013198 - Offering Business Courtesies - PRO 6
- TR007955 - Trade Secrets and Proprietary Information
- XMLSpy
- Eclipse
- Docato
- Rulesets
- Tab files
Meetings:
- Monday w/ Mark Dahl to discuss architecture of PSDD
- Monday w/ Evie Glass to discuss Stilo Tools and Authoring
- Wednesday - PartSolutions Demo
- Thursday - 3D Geometry & Tab file Author/Publish Technical Discussion
(this is an ongoing weekly meeting)
- Meet & Greet PSDD Program Mgr, Al Sanders
Concerns: Need to schedule time with someone (Mark?) to go through Docato as far as how we use it, workflow, checkin policies, and so forth.
Edited on 2008-05-09 13:23:11 by LoneGunman
Additions:
Michael Maloney's status for week of 5/5-9/2008
This week I have been getting up to speed on new hire activities, the project and development environment including:Completed Employee Training as assigned by Rao:
- TR011018 - Laptop Security Training
- TR005487 - Acceptance of Business Courtesies - Anti-Kickback
- TR013198 - Offering Business Courtesies - PRO 6
- TR007955 - Trade Secrets and Proprietary Information
- XMLSpy
- Eclipse
- Docato
- Rulesets
- Tab files
Meetings:
- Monday w/ Mark Dahl to discuss architecture of PSDD
- Monday w/ Evie Glass to discuss Stilo Tools and Authoring
- Wednesday - PartSolutions Demo
- Thursday - 3D Geometry & Tab file Author/Publish Technical Discussion
(this is an ongoing weekly meeting)
- Meet & Greet PSDD Program Mgr, Al Sanders
Concerns: Need to schedule time with someone (Mark?) to go through Docato as far as how we use it, workflow, checkin policies, and so forth.
Edited on 2008-05-06 13:04:10 by LoneGunman
Deletions:
STILO TOOLS
These are the documents Stilo provided with their Ruleset Transform and Tab File Transform Demo respectively. In testing the tools they provided, I have not found any major gaps in the Ruleset transform tools. From what I can see, they are fairly close to being production-ready. There are however, several large gaps in the Tab file transform. Stilo has provided us basically with a demo showing that they can do what we asked, but needs a lot more work to use in a production environment.There are 2 main functions of the Stilo tool:
- convert existing rulesets into XML & incorporate into the part standard XML,
- strip the ruleset XML out of the part standard & convert back into ruleset language.
The attached files are the sequence of files generated by running Stilo's ruleset transform tool. BACB30NM is used as an example - see the attached PDF version for your reference. I will describe the 2 steps above in greater detail here.
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato.
- bacb30nm-ruleset.txt∞ is the current form of all existing rulesets - this is the file I started with.
- bacb30nm-ruleset-rs.xml∞ is the ruleset as converted to XML.
- BACB30NM-merged.xml∞ is the ruleset XML merged into the part standard XML - this is the form that will reside in Docato as authoritative data. This completes step 1.
2) Ruleset Transform - This will be a Docato publication that strips out the ruleset XML from the part standard, then converts back to the ruleset language; the resulting file must be sent to the BMTdev environment for testing & approval.
- BACB30NM-ruleset.xml∞ is the ruleset XML removed from the part standard. This should be exactly the same as bacb30nm-ruleset-rs.xml∞.
- bacb30nm-ruleset-gen.txt∞ is the final ruleset as it will go out for testing & eventually production. It should be exactly the same as bacb30nm-ruleset.txt∞.
Edited on 2008-05-06 12:04:47 by LoneGunman
Additions:
- bacb30nm-ruleset.txt∞ is the current form of all existing rulesets - this is the file I started with.
Deletions:
- bacb30nm-ruleset.txt∞ is the current form of all existing rulesets - this is the file I started with.
Edited on 2008-05-06 12:01:12 by LoneGunman
Additions:
- Demo Documentation.doc
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato.
- bacb30nm-ruleset.txt∞ is the current form of all existing rulesets - this is the file I started with.
- bacb30nm-ruleset-rs.xml∞ is the ruleset as converted to XML.
- BACB30NM-merged.xml∞ is the ruleset XML merged into the part standard XML - this is the form that will reside in Docato as authoritative data. This completes step 1.
- BACB30NM-ruleset.xml∞ is the ruleset XML removed from the part standard. This should be exactly the same as bacb30nm-ruleset-rs.xml∞.
- bacb30nm-ruleset-gen.txt∞ is the final ruleset as it will go out for testing & eventually production. It should be exactly the same as bacb30nm-ruleset.txt∞.
Deletions:
- Ruleset Demo Documentation.doc
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato. Mark should have ideas on how this should be set up to run Stilo's scripts.
- bacb30nm-ruleset.txt is the current form of all existing rulesets - this is the file I started with.
- bacb30nm-ruleset-rs.xml is the ruleset as converted to XML.
- BACB30NM-merged.xml is the ruleset XML merged into the part standard XML - this is the form that will reside in Docato as authoritative data. This completes step 1.
- BACB30NM-ruleset.xml is the ruleset XML removed from the part standard. This should be exactly the same as bacb30nm-ruleset-rs.xml.
- bacb30nm-ruleset-gen.txt is the final ruleset as it will go out for testing & eventually production. It should be exactly the same as bacb30nm-ruleset.txt.
Edited on 2008-05-06 11:17:08 by LoneGunman
Additions:
- Ruleset Demo Documentation.doc
Deletions:
RulesetDemoDocumentation.doc DimensionTableDocumentation.doc
Edited on 2008-05-06 11:16:28 by LoneGunman
Additions:
STILO TOOLS
RulesetDemoDocumentation.docDimensionTableDocumentation.doc
These are the documents Stilo provided with their Ruleset Transform and Tab File Transform Demo respectively. In testing the tools they provided, I have not found any major gaps in the Ruleset transform tools. From what I can see, they are fairly close to being production-ready. There are however, several large gaps in the Tab file transform. Stilo has provided us basically with a demo showing that they can do what we asked, but needs a lot more work to use in a production environment.
Edited on 2008-05-06 11:08:28 by LoneGunman
Additions:
There are 2 main functions of the Stilo tool:
- convert existing rulesets into XML & incorporate into the part standard XML,
- strip the ruleset XML out of the part standard & convert back into ruleset language.
The attached files are the sequence of files generated by running Stilo's ruleset transform tool. BACB30NM is used as an example - see the attached PDF version for your reference. I will describe the 2 steps above in greater detail here.
1) Ruleset Conversion - converting all the current rulesets to XML and storing them in the part standards should be a one-time event. Once all rulesets are in XML form, all new rulesets must be created & authored in XML. I don't know if this conversion will be set up in Docato. Mark should have ideas on how this should be set up to run Stilo's scripts.
- bacb30nm-ruleset.txt is the current form of all existing rulesets - this is the file I started with.
- bacb30nm-ruleset-rs.xml is the ruleset as converted to XML.
- BACB30NM-merged.xml is the ruleset XML merged into the part standard XML - this is the form that will reside in Docato as authoritative data. This completes step 1.
2) Ruleset Transform - This will be a Docato publication that strips out the ruleset XML from the part standard, then converts back to the ruleset language; the resulting file must be sent to the BMTdev environment for testing & approval. Collin Bennett & Greg Kahler should be able to tell you more about the BMTdev end of it.
- BACB30NM-ruleset.xml is the ruleset XML removed from the part standard. This should be exactly the same as bacb30nm-ruleset-rs.xml.
- bacb30nm-ruleset-gen.txt is the final ruleset as it will go out for testing & eventually production. It should be exactly the same as bacb30nm-ruleset.txt.
Edited on 2007-11-18 17:43:48 by LoreWeaver
Additions:
where each can be a range between 1-254 and where $ip4 = 254 increment ip3 by 1
(++)then run through the first loop again til 254, increment ip3 again, loop, etc.
Deletions:
where each can be a range between 1-254 and where $ip4 = 254 increment ip3 by 1 () then run through the first loop again til 254, increment ip3 again, loop, etc.
Edited on 2007-11-18 17:42:11 by LoreWeaver
Additions:
Meditation on Clear Wisdom
We will be discussing the "Path of Accumulation" in which the bodhisattva accumulates merit through perfection of various actions such as moral discipline, patience, effort, and so forth. We are now hearing the specific instructions in how to perfect wisdom in order to attain a union of tranquil abiding and superior seeing, which we will need in order to develop a correct inferential realization of emptiness, and thus enter we can enter the "Path of Preparation"Clear Wisdom is wisdom that discerns its object clearly and precisely. If we can understand with ease whatever we attempt to understand, if we have clear memory and imagination, and if we can distinguish the subtlest topics such as impermanence and emptiness, this indicates that we have clear wisdom. With clear wisdom we can clearly recall what has been understood. Clear wisdom brings clear concentration which we will need in order to progress on the path to preparation.
Edited on 2007-11-15 22:51:44 by LoreWeaver
Deletions:
BloodSugar
Edited on 2007-10-22 13:29:08 by LoreWeaver
Additions:
BloodSugar
Edited on 2006-05-09 20:25:32 by LoreWeaver
Additions:
Think of it this way. You have two variables:
$ip3 = 1;
$ip4 = 1;
where each can be a range between 1-254 and where $ip4 = 254 increment ip3 by 1 () then run through the first loop again til 254, increment ip3 again, loop, etc.
Edited on 2006-05-09 19:53:29 by LoreWeaver
Additions:
Looping: The + operator is overloaded to enable looping through a range.
Example:
(++$x)
Deletions:
Looping: The + operator is overloaded to enable looping through a range. Example:
(++$x)
Edited on 2006-05-09 19:53:13 by LoreWeaver
Additions:
Looping: The + operator is overloaded to enable looping through a range. Example:
(++$x)
Deletions:
Looping: The + operator is overloaded to enable looping through a range. Example: ($x)
Oldest known version of this page was edited on 2006-05-09 19:52:24 by LoreWeaver []
Page view:
NotePad
Net::IP
Looping: The + operator is overloaded to enable looping through a range. Example: ($x)
my $ip = new Net::IP ('195.45.6.7 - 195.45.6.19') || die;
# Loop
do {
print $ip->ip(), "\n";
} while (++$ip);
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License.
© 2007 LoreWeaver