This repository has been archived by the owner on Feb 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Generic markdown #2
Open
EvanMPutnam
wants to merge
13
commits into
master
Choose a base branch
from
generic_markdown
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
8047d65
Made markdown_compile.py fairly generic for whatever docs the user wants
EvanMPutnam d7de060
Updating .bat file
EvanMPutnam 16900b6
Deleteing extra .tex and .pdf file from a previous compile
EvanMPutnam b6b8286
Updating markdown_compiler with generic logging functionality.
EvanMPutnam d1678ef
Removing log files and updating docs
EvanMPutnam 508e9a8
minor formatting tweaks
runphilrun 6971a9f
Merge branch 'master' into generic_markdown
runphilrun adbe9ec
add toc to readme
runphilrun ac56fbc
break long lines and other formatting
runphilrun d71eb67
add markdown to tex compiler instructions to readme
runphilrun 5611a76
rename directory for markdown to tex compiler
runphilrun 82e524d
log debug statements even if not verbrose
runphilrun fa16d3a
make relative path
runphilrun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,17 @@ | ||
@echo OFF | ||
|
||
REM This is a .bat file that can be used to compile a markdown file using a latex template file. | ||
REM The latex template file has variables/sections that are populated from the markdown file. | ||
REM This is a Windows file and there should be a corresponding linux/macos compile script. | ||
|
||
REM This is where you specify the path of your document. | ||
set DOCUMENT_PATH="markdown_template.md" | ||
set DOCUMENT_PATH="Templates\\markdown_template.md" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should these be arguments instead? or maybe a config file? |
||
|
||
REM This is where you specify the final name of your document. Spaces will be replaced with underscores. | ||
set FINAL_DOC_NAME="50_SAT" | ||
|
||
REM This is the where you specify the template of the .tex file. | ||
set PDD_TEMPLATE="spex_template.tex" | ||
set PDD_TEMPLATE="Templates\\PDD_Template.tex" | ||
|
||
REM You can specify the type of compiler script. It expects an input of the path of the .tex document. | ||
set COMPILE_SCRIPT="..\\Compile_Scripts\\MikTexCompiler.bat" | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,7 +43,7 @@ | |
\makenomenclature{} | ||
|
||
% set title. choose something as descriptive and precise as possible. Descriptive > sounding cool. remember this! | ||
\title{TITLETAG} | ||
\title{TITLE_TAG} | ||
|
||
|
||
\author{ | ||
|
@@ -56,13 +56,13 @@ | |
% Read here for a more advanced options to modifying footnotes in the author block: \url{http://tex.stackexchange.com/questions/826/symbols-instead-of-numbers-as-footnote-markers} | ||
% Here, we use the IEEE long-form author block. | ||
\IEEEauthorblockN{% This block is for author Names. | ||
STUDENTTAG%\IEEEauthorrefmark{1}, | ||
AUTHORS_TAG%\IEEEauthorrefmark{1}, | ||
} | ||
\IEEEauthorblockA{% This block is for the author Afficliations, aka department and university | ||
RIT Space Exploration, Rochester Institute of Technology \\ %\\ starts a new line | ||
Rochester, N.Y. \\ | ||
Email: | ||
EMAILTAG%\IEEEauthorrefmark{1}[email protected], | ||
EMAIL_TAG%\IEEEauthorrefmark{1}[email protected], | ||
} | ||
%% Below, we use the short-form author block and basically hack it to suit our needs. | ||
% Philip~Linden$^{*\dagger}$% | ||
|
@@ -86,17 +86,17 @@ | |
%% There are ways to make LaTeX do this for you, but it is more advanced and not entirely necessary, especially for short author lists. Not worth the hassle, in my opinion. | ||
} | ||
% page header for pages other than cover page | ||
\markboth{TITLETAG}% | ||
\markboth{TITLE_TAG}% | ||
{Tarazevits \MakeLowercase{\textit{et al.}}: RIT Space Exploration} | ||
|
||
% Initial setup is over, start building the document itself | ||
\begin{document} | ||
\maketitle% | ||
\maketitle | ||
% correct bad hyphenation here, separated by spaces | ||
\hyphenation{explor-ation} | ||
|
||
\begin{abstract} | ||
ABSTRACTTAG | ||
ABSTRACT_TAG | ||
|
||
% The abstract is a brief summary of the design document. Typically it includes the purpose of the design document, key goals or objectives, and justifications. | ||
% Be sure not to confuse the abstract with the introduction. | ||
|
@@ -128,7 +128,7 @@ | |
\nomenclature{CSLI}{CubeSat Launch Initiative} | ||
\nomenclature{AMSAT}{Amateur Radio in Space} | ||
|
||
SECTIONTAG | ||
SECTION_TAG | ||
|
||
\bibliography{SPEX50SAT} | ||
\onecolumn | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,127 @@ | ||
--- | ||
TITLE_TAG: 50\$ Satellite PDD AUTHORS_TAG: Evan Putnam, Another Student | ||
EMAIL_TAG: [email protected], [email protected] TEMP_TAG: Hello World | ||
--- | ||
<!--- | ||
This is a template you can use for markdown with the SPEX PDD LaTeX documents. | ||
Specify a title, authors, and emails. | ||
|
||
Current Features: | ||
Sections | ||
Subsections | ||
Text and newlines. | ||
Basic LaTeX syntax (as long as no LaTeX or regular comments are inside a statement). | ||
|
||
Commenting: | ||
Multiline comments are only supported if you have a single start and | ||
end on a separate line. For example you can not start a new comment on | ||
the same line as an ending tag for a multiline comment. | ||
|
||
There can only be one single line comment per line. | ||
Nested comments are not supported. | ||
|
||
Important notes and potential gotchas: | ||
Comments. | ||
New lines. | ||
---> | ||
|
||
<!--- | ||
This is a special section that SHOULD exist. | ||
This is text for your abstract and should appear before other sections. This | ||
CAN NOT have sub-sections and MUST have the # ABSTRACT syntax. | ||
---> | ||
# ABSTRACT | ||
HERE BE A BIG HONKING ABSTRACT! | ||
|
||
# Section 1 | ||
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor | ||
incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis | ||
nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. | ||
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu | ||
fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in | ||
culpa qui officia deserunt mollit anim id est laborum. | ||
|
||
## Subsection 1.1 | ||
Hey how is it going?<!--- This is a single line comment which can be put | ||
anywhere! Only one per line. ---> | ||
|
||
<!--- Completely blank lines are treated as a line break.---> | ||
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor | ||
incididunt ut labore et dolore magna aliqua. | ||
<!--- Comment lines are not.---> | ||
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut | ||
aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in | ||
voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint | ||
occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim | ||
id est laborum. | ||
|
||
## Subsection 1.2 | ||
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor | ||
incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis | ||
nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. | ||
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu | ||
fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in | ||
culpa qui officia deserunt mollit anim id est laborum. | ||
|
||
|
||
# Section 2 | ||
Here is another section! | ||
|
||
## Subsection 2.1 | ||
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor | ||
incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis | ||
nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. | ||
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu | ||
fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in | ||
culpa qui officia deserunt mollit anim id est laborum. | ||
|
||
# Section 3 | ||
## Subsection 3.1 | ||
You can also include subsections where the section does not include text. | ||
|
||
|
||
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor | ||
incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis | ||
nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. | ||
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu | ||
fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in | ||
culpa qui officia deserunt mollit anim id est laborum. | ||
|
||
# Section 4 | ||
## LaTeX Tables | ||
|
||
<!--- You can use standard LaTeX syntax if it can be put on a single line. ---> | ||
This is a table \autoref{table:somechart} | ||
|
||
<!--- | ||
This command counts as being on a single line. | ||
Here is LaTeX code to create a table. | ||
---> | ||
\begin{table} | ||
\centering | ||
\caption{Estimated Timeline} | ||
\begin{tabularx}{\columnwidth}{@{}cXl@{}} \toprule | ||
Phase & Task & Duration \\ \midrule | ||
1 & Review existing \$50SAT designs and materials & 2 weeks or less \\ | ||
2 & Subsystem development & 6 weeks \\ | ||
& Order PCB design and/or assembly & 6 weeks \\ | ||
& Review changes to mechanical strucuture and order materials & 2 weeks or less \\ | ||
& Testing of individual subsystems & 2 weeks \\ | ||
3 & System Assembly & 1 week \\ | ||
4 & System testing & 2 weeks \\ | ||
5 & Generate documentation and delivery to SPEX & 1 week \\ | ||
\bottomrule | ||
\end{tabularx} | ||
\label{table:somechart} | ||
\end{table} \\ | ||
|
||
<!--- | ||
This command counts as being on a single line. | ||
Here is an example of inserting an image in your document. | ||
Image is one directory up of final folder so uses ../ formatting. | ||
---> | ||
\begin{figure}[h] | ||
\centering | ||
\includegraphics[width=12cm, height=9cm]{../spex.png} | ||
\caption{Here is the SPEX Logo.} | ||
\end{figure} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
an equivalent shell script should be created in order to run this in non-windows environments (for example, I use
.sh
scripts with Windows Subsystem for Linux and almost never touch Powershell)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Want to do this in a separate cross-platform branch