Hi everybody,
I'm a total noob concerning programming and electronics. I'v build my own emontx V2 which was hard for me. I followed all the instructions on the site to build the emontx and now I'am finished with the job.
I also installed the arduino environment and want to start with programming the board. But before I continue how can I check that my board works fine?
Are there a series of simple tests I can perform the check the health status of the emontx?
As you can see in the picture the green led is isn't turn on. So I'm afraid something went wrong during soldering. However the voltage check before soldering the rfm chip was fine.
thx
Re: trying to start my emontx v2
I assume you did all the voltage checks as you were building the emonTx?
First, you need the Arduino IDE on your computer. Instructions for getting and loading it are in Building Blocks > Setting up the Arduino Environment.
Your programmer is upside down! Line up the GND pins.
Next, you need to load a sketch.
I suggest the emonTx V2 version of the default sketch that comes with the later V3 versions. You will find it on GitHub > emonTxFirmware > emonTxV2 > emonTx_CT123_Voltage. You need both the files in that directory. Download both files into a directory in your sketchbook folder called "emonTx_CT123_Voltage". If you can compile and load that, then that is the first hurdle overcome.
If it prints the introduction "emonTX CT123 Voltage example" etc and then nothing more and the LED stays on for a long time, you have a problem with your RFM12B module.
If the LED stays on for about 5 s, then flashes once every 5 s, that's good.
Connect an ac adapter and check the serial output. It should be printing 4 values on each line, accompanied by a flash on the LED. The first three are power and should be zero or a small number, the 4th is your mains voltage.
Plug in a ct to input 1 and clip it over the line conductor only of a load - say an electric kettle. The 1st power should read the kettle power (3000 or so). If both those things happen, then most of it seems to be working. You can check the other 2 current inputs likewise.
If all is well, you can calibrate it properly. Instructions are in Building Blocks.
Re: trying to start my emontx v2
To get the LED to glow, you just need a sketch which drives IO pin 9 high.
If you load blink.ino from the Examples area in your Arduinio IDE, then change the three occurrences of "13" to "9" and reload, the green LED should start blinking. It's a great feeling when it does!
(blink.ino is at File->Examples->01.Basics->Blink)
The LED does have to be the correct way round, otherwise it will never turn on. In your photo, the flat on the LED needs to be towards the bottom of the picture.
Re: trying to start my emontx v2
I turned the programmer upside down. Is it ok now?
Ok, i compiled the code for blink.ino and i have no compiling errors
Uploading the code to the emontx is a problem. I installed the arduino software in C:\temp
can that be the problem?
I didn't try the solution of robert. Will do later on today
Re: trying to start my emontx v2
First, you will have to get your code to upload into the processor. The IDE will show "Uploading..." and then "Done uploading."
blink.ino is a good sketch to use for this purpose. As soon as this sketch has been uploaded, your LED should start to blink.
Then, you can try a more complex sketch ...
Re: trying to start my emontx v2
uploading the simple code doesn't work.
Gonna use the multimeter to test the components. I'll keep you posted
Re: trying to start my emontx v2
Yes, stay with blink.ino until you have that working. I can't quite tell some of the colour bands on the resistors, those that I can see look OK. So nothing stands out as being obviously wrong.
Have you installed your Arduino IDE and USB Drivers according to the instructions here, or Arduino's instructions?
Re: trying to start my emontx v2
The first thing to check is the settings for the Arduino upload facility. What COM port is it set to use? That should be the same as the COM port for the USB programmer. If you didn't install the drivers for the programmer or set the COM port, that would explain the inability to upload.
Re: trying to start my emontx v2
I've told Hulda to set up the IDE according to the instructions on this site, then asked if it has been. If that's not been done (i.e. he's using the Arduino drivers which we know don't work, and that's why I asked), there's little anyone can do to help.
Re: trying to start my emontx v2
hello,
I attached two screenshots
according to me the driver and the correct com port are selected no?
Re: trying to start my emontx v2
Yes, those appear to be correct.
Which version of Windows is it?
Is anything else attempting to use COM 5?
I thought in one of your earlier pictures that the programming header connector pins were not quite in line exactly. Is that in fact OK?
Re: trying to start my emontx v2
For a quick test of the com port and programmer, if you short the rx and tx pins of the ftdi programmer together with a piece of wire or a paper clip etc (without the emonTx connected) anything you type in the arduino IDE's serial console should echo back and appear in the 2nd textbox of the console when you press send.
Paul
Re: trying to start my emontx v2
@Robert Hall - You are right. they are not in line. I'll try to fix it this weekend
Re: trying to start my emontx v2
@pb66 - I'll try to test it this at lunchbreak - i'll keep your posted
Re: trying to start my emontx v2
Thanks pb66, that's a great test.
Here, I've joined the two serial pins together with a low valued resistor, but it works fine. Any characters that are typed into the upper 'send' box in the IDE then appear in the lower 'received data' box when the [Enter] key is pressed.
(sorry if this image is over-size. Not sure how to make it smaller)
Re: trying to start my emontx v2
Hi,
I joined the pins together with a piece of solderwire, tested it and.... Still nothing
I didn't bought the usb cable in the shop of openenergy. Can that be the problem? it's my own usb cable
Re: trying to start my emontx v2
You could check the cable with a multimeter, but can you plug the programmer (which is from the OEM shop) directly into your computer and then try joining the pins (RXD - TXD) again? If that does work, your cable is faulty. If it does not, then I think the drivers are not installed correctly. Which version of Windows do you have?
Re: trying to start my emontx v2
I use windows 7 and this is a screenshot of my driver settings
Re: trying to start my emontx v2
You posted 2 screenshots, one showing you are on COM2 and another one on COM5.
Try to set your Arduino environment on the same COM port you are using.
Re: trying to start my emontx v2
it's true that i posted 2 screenshots with different com-ports that's because i reinstalled everything and tried other ports and so on.
Re: trying to start my emontx v2
I have access only to Windows XP or Windows 8.1, so I'm sorry I cannot help there.
Re: trying to start my emontx v2
If that can be of any help, I have installed the Windows 7 driver downloaded from that site: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
However, I bought the USB bridge in the OpenEnergyMonitor shop.
Re: trying to start my emontx v2
yes daturach i installed these drivers already a 1000 times. When I attach the programmer, the device is detected by the device manager of win7.
I'am about to throw the towel...
can i alse use a simple ftdi-cable to program the emontxV2?
I can also buy a new programmer and a usb cable on the openenergy site before i get nuts. Pfff...
Re: trying to start my emontx v2
To program an Arduino Uno, only a standard USB cable is needed (no programmer or extra drivers). The emonTx requires the USB/USART programmer and a (different) USB cable. Because they both have the same processor on board, the Arduino and emonTx can run exactly the same software.
An Arduino may be an easy way for you to get started ...
Re: trying to start my emontx v2
Do you have access to a linux PC or Raspberry Pi ? the shop bought FTDI programmer doesn't need any drivers on linux. so you could easily determine if your programmer and lead are ok or not if you do.
If you do not, you could download a free linux live OS image to a usb stick and temporarily reboot your pc to linux.
If you do find your lead/programmer is at fault and you do have a Pi and 5x F-F link wires you could easily program the emonTx directly from the Pi without a programmer, it's easier to use either a Pi with a monitor/keyboard or my preference is to use windows "Remote Desktop Connection".
Paul
Re: trying to start my emontx v2
This is Windows 8.1, but Windows 7 is similar.
Plug your programmer (which is from the OEM shop?) directly into your computer and then try joining the pins (RXD - TXD) again. Can you type a message:
click "Send" and does it appear here?
If your message appears in the large window, your drivers and programmer are working.
Re: trying to start my emontx v2
owkay,
@Calypso I'am using a regular usb cable. I thought all usb cables were the same. If that is the cause, then I'am so stupid.
@pb66: Yes I have an raspberry pi but no 5x FF link wire
@ Robert, I bought the programmer at the OEM shop but nog the usb cable. My usb cable is a standard usb cable. Is a different usb cable required? Anyway the test i did(joining the Rx en Td-pin was positive. What now?
Re: trying to start my emontx v2
The programmer and drivers are both good.
Now repeat the test with your USB cable between your computer and the programmer. If the test fails, the problem is your cable. If it passes, the problem is in your emonTx.
All USB cables should be wired the same. If the cable fails, you might find the fault with a multimeter - one or more wires open-circuit or a short-circuit between two wires, or a faulty connector at either end.
Re: trying to start my emontx v2
That is good news.
Now you should connect the emontx inplace of the link and start the arduino IDE (make sure all previous instances were closed first) to see if you can communicate with the emonTx by uploading "blink".
Can you confirm if the MCU (the ATmega328P) has the bootloader installed? Did you get a kit from the shop or source your own parts? You can only use the FTDI programmer to load sketches via serial IF there is already a bootloader.
The USB leads can differ but as rule if it plugs in it should work. I think Robin and Robert are picturing a USB-A to USB-A lead as our programmers are USB-A, where as yours is the newer micro usb style, I believe.
Paul
Re: trying to start my emontx v2
Hi Robert - looking at the pic in the OP the programmer has a micro usb so I assume the test must of been with lead in-line.
Paul
Re: trying to start my emontx v2
Unless Hulda has a micro-micro extension and a converter at the computer end, or a computer with a micro. Whichever, we're getting closer to the fault.
Re: trying to start my emontx v2
yes, i bought all my components in the OEM shop including the chip. My usb cable is a mini usb.
If I try to upload the blink programme, it fails.
So there is a problem with my emontx.
when soldering I did the voltage check before soldering the rfm12B module. I had the 3.3 v
After soldering when I check the same Pins I got les then 1v. Is this normal?
Re: trying to start my emontx v2
There is definitely a problem there. You should read 3.3 V between Bat + and Bat - (Those are the same as Vcc and GND.)
Look for a fine strand of solder between any two pins of your RFM12B, particularly the two next to the antenna. Those are Vcc and GND.
If you cannot see a fault in your soldering, it is possible that you have a faulty RFM12B.
The very first thing you do when you are testing anything is check the power supplies.
Re: trying to start my emontx v2
Ok, on Bat + en Bat - I have 0.6V and and the RFM12B I have also 0.6V
All the other GND+PWR give me 4.7V
I tried to remove the RFM12B but it's impossible.
The only option left is to start from scratch and order the a new emontxV2 :(
Fingers crossed...
Thx everybody for your patience and your help. You guys are all so helpful. This is a great community and i'll try to convince my father and brother who have also solar panels to invest in your monitor technology
Re: trying to start my emontx v2
Let us see what Glyn or Trystan say before you start again.
Re: trying to start my emontx v2
One final thought:
Can you unplug the processor and then check the voltages again?
Re: trying to start my emontx v2
I also wonder if there is any value in whipping out the voltage regulator, could a prolonged use of an inverted programmer cause it to fail? a point could be proved by then tacking a link wire from the ftdi p5 to a 3.3v point (eg batt+) to power up direct from the programmer. ???
Paul
Re: trying to start my emontx v2
I removed the processor but the DIL is still on the pcb - still no result
@pb66 I'll try your proposition this afternoon. I'll post the results here
Re: trying to start my emontx v2
Hi,
The progammer works fine because the voltage onto the FTDI pins is 3.3V.
BTW: is it normal that the MCP1702 is so hot that you can't touch it?
As you can see I did the test but I have only 0.6V on the bat+ and bat- and the programmer becomes so hot that it's starting to smell a bit.
Re: trying to start my emontx v2
STOP !!!!
Disconnect the programmer
Appologies for shouting but didn't want you to fry anything in the time it took me to write a full post
"BTW: is it normal that the MCP1702 is so hot that you can't touch it?" no it isn't !
My suggestion was to REMOVE the voltage reg and power via the programmer, NOT bypass while still in place.
Was it getting hot before you out the link on of just after? if it was hot before there is definitely a short on the board.
Paul
Re: trying to start my emontx v2
I already disconnected the programmer and tested it and it is still functioning fine.
The MCP1702 was already getting hot from the very beginning I assembled the emontx
My suggestion was to REMOVE the voltage reg and power via the programmer - I'm sorry I don't know how to do that
Re: trying to start my emontx v2
I suspect the MCP1702 voltage regulator (reg) was ok prior to the fitment of the rfm board as you state the voltage was ok then but not after. Have you checked for shorts visually with a magnifying glass ? most likely on the rfm pads.
Re: trying to start my emontx v2
yes I checked for shorts visually with a magnifying glas and magnified pictures. I cannot see any of it.
Re: trying to start my emontx v2
Sorry to hear that your having trouble. It could be you have a faulty rf module. If you want to send the board back to us we would be happy to try and take a look at it for you. Thanks for trying help guys
Re: trying to start my emontx v2
Hulda, I have several emonTx V2 boards here that I no longer have any use for. Most if not all have an 868 MHz RF module in place. If you send me a PM with your address, you're welcome to one of them. Some channels may not be populated, but the board should work OK. This will allow you to upload sketches and run some simple checks.
Re: trying to start my emontx v2
From the picture in the first post, it's a 433 MHz module that Hulda has.
Re: trying to start my emontx v2
OK, but the problems that have been discussed on this thread appear to be more fundamental than this; nothing is working and the Vreg is overheating.
Over short distances, an 868 MHz RFM12B can apparently function satisfactorily at 433 MHz. Replacing the RF module is not a simple task on this board.
Re: trying to start my emontx v2
I wanted to point out that you kind offer won't help Hulda very much, because although he can do as you suggest, the radio range on the wrong band is not good, so unless you have a non-radio V2, he still has the problem of removing the RFM12B, and that needs specialist tools.
We still don't know the real problem, but Hulda assembled the board up to installing the RFM12B, and all was well, then he completed the assembly and it didn't work. But in the screen shot attached to the first post, the programmer is upside down meaning that TXD got the 5 V supply, RXD got the 3.3 V supply, RTS was programmer GND, the 5 V rail got TXD and GND got RTS which is used as the reset. The 3.3 V connection on the emonTx is not used. The emonTx 3.3 V comes from the programmer 5 V via the MCP1702, the 3.3 V regulator, which appears to be shorted to GND via 1 forward-biased junction. And it apparently is not the processor as he's still got the fault with that removed.
I don't think Paul's suggestion that the MCP1702 saw a reversed voltage is correct, because reversing the programmer on the header does not swap the 5 V supply over.
Re: trying to start my emontx v2
I tend to agree the 'short' is most likely rfm related, the 'reg removal' suggestion was prior to checking the schematic as I thought it was easier to remove than the rfm board to reach a conclusion but the fact the MCP1702 has been hot since the rfm was fitted is pretty conclusive too.
I think the best thing to do is to send it off to Glyn, Nice offer though Robin!
Paul
Re: trying to start my emontx v2
Hulda has told us that the 3.3 V rail was OK before adding the RFM12B, but I'm not aware that he has ever been able to upload a sketch to this board. Maybe he would be able to confirm this.
I could probably find a non-RF emonTx V2 in my collection but it may have some other bits & pieces on board.


| RFC 2629 |
| TOC |
|
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (1999). All Rights Reserved.
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.
| RFC 2629 |
| TOC |
| TOC |
This memo describes how to write a document for the I-D and RFC series using the Extensible Markup Language[1] (XML). This memo has three goals:
It is beyond the scope of this memo to discuss the political ramifications of using XML as a source format for RFC-like documents. Rather, it is simply noted that adding minimal markup to plain text:
| TOC |
We do not provide a formal or comprehensive description of XML. Rather, this section discusses just enough XML to use a Document Type Declaration (DTD) to write RFC-like documents.
If you're already familiar with XML, skip to The RFC DTD to look at the DTD.
There are very few rules when writing in XML, as the syntax is simple. There are five terms you'll need to know:
First, start your source file with an XML declaration, a reference to the DTD, and the "rfc" element:
<?xml version="1.0"?> <!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <rfc> ... </rfc>
Ignore the first two lines -- the declaration and the reference -- and simply treat them as opaque strings. Nothing else should be present after the "</rfc>" tag.
Second, make sure that all elements are properly matched and nested. A properly matched element that starts with "<example>" is eventually followed with "</example>". (Empty elements are always matched.) Elements are properly nested when they don't overlap.
For example,
<outer> ... <inner> ... </inner> ... </outer>
is properly nested.
However,
<outer> ... <inner> ... </outer> ... </inner>
overlaps, so the elements aren't properly nested.
Third, never use "<" or "&" in your text. Instead, use either "<" or "&", respectively.
Fourth, there are two quoting characters in XML, 'apostrophe' and "quotation". Make sure that all attributes values are quoted, e.g., "<example name='value'>", If the value contains one of the quoting characters, then use the other to quote the value, e.g., "<example name='"'>", If the value contains both quoting characters, then use one of them to quote the value, and replace occurrances of that character in the attribute value with either ''' (apostrophe) or """ (quotation), e.g., "<example name='"'"'>".
If you want to put a comment in your source file, here's the syntax:

Finally, XML is case sensitive.
Immediately following the "<rfc>" tag is the "front" element:
<?xml version="1.0"?> <!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <rfc> <front> <title ...> <author ...> <author ...> <date ...> <area ...> <workgroup ...> <keyword ...> <keyword ...> <abstract ...> <note ...> </front> ... </rfc>
(Note that in all examples, indentation is used only for expository purposes.)
The "front" element consists of a "title" element, one or more "author" elements, a "date" element, one or more optional "area" elements, one or more optional "workgroup" elements, one or more optional "keyword" elements, an optional "abstract" element. and, one or more optional "note" elements.
The "title" element identifies the title of the document. Because the title will be used in the headers of the document when formatted according to [2], if the title is more than 42 characters, then an abbreviation should also be provided, e.g.,
<title abbrev="Much Ado about Nothing"> The IETF's Discussion on "Source Format of RFC Documents" </title>
Each "author" element identifies a document author. Since a document may have more than one author, more than one "author" element may be present. If the author is a person, then three attributes must be present in the "<author>" tag, "initials", "surname", and "fullname", e.g.,
<author initials="M.T." surname="Rose" fullname="Marshall T. Rose">
The "author" element itself consists of an "organization" element, and, an optional "address" element.
The "organization" element is similar to the "title" element, in that an abbreviation may be paired with a long organization name using the "abbrev" attribute, e.g.,
<organization abbrev="ISI"> USC/Information Sciences Institute </organization>
The "address" element consists of an optional "postal" element, an optional "phone" element, an optional "facsimile" element, an optional "email" element, and, an optional "uri" element.
The "postal" element contains one or more "street" elements, followed by any combination of "city", "region" (state or province), "code" (zipcode or postal code), and "country" elements, e.g.,
<postal> <street>660 York Street</street> <street>M/S 40</street> <city>San Francisco</city> <region>CA</region> 94110 <country>US</country> </postal>
This flexibility is provided to allow for different national formats for postal addresses. Note however, that although the order of the "city", "region", "code", and "country" elements isn't specified, at most one of each may be present. Regardless, these elements must not be re-ordered during processing by an XML application (e.g., display applications must preserve the ordering of the information contained in these elements). Finally, the value of the "country" element should be a two-letter code from ISO 3166.
The "phone", "facsimile", "email", and "uri" elements are simple, e.g.,
<phone>+1<PHONE_NUMBER></phone><EMAIL_ADDRESS><uri>http://invisible.net/</uri>
The "date" element identifies the publication date of the document. It consists of a month and a year, e.g.,
<date month="February" year="1999" />
The "date" element also has an optional day attribute.
The "front" element may contain meta data -- the content of these elements does not appear in printed versions of the document.
A document has one or more optional "area", "workgroup" and "keyword" elements, e.g.,
<area>General</area> <workgroup>RFC Beautification Working Group</workgroup> <keyword>RFC</keyword> <keyword>Request for Comments</keyword> <keyword>I-D</keyword> <keyword>Internet-Draft</keyword> <keyword>XML</keyword> <keyword>Extensible Markup Language</keyword>
The "area" elements identify a general category for the document (e.g., one of "Applications", "General", "Internet", "Management", "Operations", "Routing", "Security", "Transport", or "User"), while the "workgroup" elements identify the IETF working groups that produced the document, and the "keyword" elements identify useful search terms.
A document may have an "abstract" element, which contains one or more "t" elements. In general, only a single "t" element is present, e.g.,
<abstract> <t>This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.</t> </abstract>
A document may have one or more "note" elements, each of which contains one or more "t" elements. There is a mandatory "title" attribute. In general, the "note" element contains text from the IESG, e.g.,
<note title="IESG Note"> <t>The IESG has something to say.</t> </note>
Note that text relating to the memo's status, copyright notice, or table of contents is not included in the document's markup -- this is automatically inserted by an XML application when it produces either a text or HTML version of the document.
If an Internet-Draft is being produced, then the "ipr" attribute should be present in the "<rfc>" tag at the beginning of the file. The value of the attribute should be one of:
- full2026:
- indicating that the document is in full conformance with all the provisions of Section 10 of RFC 2026;
- noDerivativeWorks2026:
- indicating that the document is in full conformance with all the provisions of Section 10 of RFC 2026 except that the right to produce derivative works is not granted; or,
- none:
- indicating that the document is NOT offered in accordance with Section 10 of RFC 2026, and the author does not provide the IETF with any rights other than to publish as an Internet-Draft.
In the latter case, a copyright notice will not be automatically inserted during processing by an XML application.
Consult [3] for further details.
Finally, if the Internet-Draft is being submitted to an automated process, then the "docName" attribute should be present in the "<rfc>" tag at the beginning of the file. The value of this attribute contains the document (not file) name associated with this Internet-Draft, e.g.,
<rfc ipr="full" docName="draft-mrose-writing-rfcs-01"> ... </rfc>
So, putting it all together, we have, e.g.,
<front> <title>Writing I-Ds and RFCs using XML</title> <author initials="M.T." surname="Rose" fullname="Marshall T. Rose"> <organization>Invisible Worlds, Inc.</organization> <address> <postal> <street>660 York Street</street> <street>M/S 40</street> <city>San Francisco</city> <region>CA</region> 94110 <country>US</country> </postal> <phone>+1<PHONE_NUMBER></phone><EMAIL_ADDRESS><uri>http://invisible.net/</uri> </address> </author> <date month="February" year="1999" /> <area>General</area> <workgroup>RFC Beautification Working Group</workgroup> <keyword>RFC</keyword> <keyword>Request for Comments</keyword> <keyword>I-D</keyword> <keyword>Internet-Draft</keyword> <keyword>XML</keyword> <keyword>Extensible Markup Language</keyword> <abstract> <t>This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.</t> </abstract> </front>
The "middle" element contains all the sections of the document except for the bibliography and appendices:
... </front> <middle>

 </middle> <back> ...
The "middle" element consists of one or more "section" elements.
Each "section" element contains a section of the document. There is a mandatory attribute, "title", that identifies the title of the section. There is also an optional attribute, "anchor", that is used for cross-referencing with the "xref" element, e.g.,

 ...

The "section" element is recursive -- each contains any number and combination of "t", "figure", and "section" elements, e.g.,

 ...
 ...
...

...

...

...

...

...

The "t" element contains any number and combination of paragraphs, lists, and figures. If a cross-reference is needed to a section, figure, or reference, the "xref" element is used; similarly, if an external-reference is needed, the "eref" element is used. Indexing of text is provided by the the "iref" element.
The "list" element contains one or more items. Each item is a "t" element, allowing for recursion, e.g.,
<list style="numbers"> <t>The first item.</t> <t>The second item, which contains two bulleted sub-items: <list style="symbols"> <t>The first sub-item.</t> <t>The second sub-item.</t> </list> </t> </list>
The "list" element has an optional attribute, "style", having the value "numbers" (for numeric lists), "symbols" (for bulleted lists), "hanging" (for hanging lists), or, "empty" (for indented text). If a "list" element is nested, the default value is taken from its closest parent; otherwise, the default value is "empty".
When nested within a "hanging list" element, the "t" element has an optional attribute, "hangText" that specifies the text to be inserted, e.g.,
<list style="hanging"> <t hangText="full2026:">indicating that the document is in full conformance with all the provisions of Section 10 of RFC 2026;</t> <t hangText="noDerivativeWorks2026:">indicating that the document is in full conformance with all the provisions of Section 10 of RFC 2026 except that the right to produce derivative works is not granted; or,</t> <t hangText="none:">indicating that the document is NOT offered in accordance with Section 10 of RFC 2026, and the author does not provide the IETF with any rights other than to publish as an Internet-Draft.</t> </list>
The "figure" element groups an optional "preamble" element, an "artwork" element, and an optional "postamble" element together. The "figure" element also has an optional "anchor" attribute that is used for cross-referencing with the "xref" element. There is also an optional "title" attribute that identifies the title of the figure.
The "preamble" and "postamble" elements, if present, are simply text. If a cross-reference is needed to a section, figure, or reference, the "xref" element is used; similarly, if an external-reference is needed, the "eref" element is used. Indexing of text is provided by the the "iref" element.
The "artwork" element, which must be present, contains "ASCII artwork". Unlike text contained in the "t", "preamble", or "postamble" elements, both horizontal and vertical whitespace is significant in the "artwork" element.
So, putting it all together, we have, e.g.,

 <preamble>So, putting it all together, we have, e.g.,</preamble> <artwork> ascii artwork goes here... be sure to use "<" or "&" instead of "<" and "&", respectively! </artwork> <postamble>which is a very simple example.</postamble>

which is a very simple example.
If you have artwork with a lot of "<" characters, then there's an XML trick you can use:

 <preamble>If you have artwork with a lot of "<" characters, then there's an XML trick you can use:</preamble> <artwork><![CDATA[ ascii artwork goes here... just don't use "]]" in your artwork! ]]></artwork> <postamble>The "<![CDATA[ ... ]]>" construct is called a CDATA block -- everything between the innermost brackets is left alone by the XML application.</postamble>

The "<![CDATA[ ... ]]>" construct is called a CDATA block -- everything between the innermost brackets is left alone by the XML application.
Because the "figure" element represents a logical grouping of text and artwork, an XML application producing a text version of the document should attempt to keep these elements on the same page. Because RFC 2223[2] allows no more than 69 characters by 49 lines of content on each page, XML applications should be prepared to prematurely introduce page breaks to allow for better visual grouping.
Finally, the "artwork" element has two optional attributes: "name" and "type". The former is used to suggest a filename to use when storing the content of the "artwork" element, whilst the latter contains a suggestive data-typing for the content.
The "xref" element is used to cross-reference sections, figures, and references. The mandatory "target" attribute is used to link back to the "anchor" attribute of the "section", "figure", and "reference" elements. The value of the "anchor" and "target" attributes should be formatted according to the token syntax in XML basics.
If used as an empty element, e.g.,
according to the token syntax in <xref target="xml_basics" />.
then the XML application inserts an appropriate phrase during processing, such as "Section 2.1" or "XML Basics".
If used with content, e.g.,
conforming to <xref target="refs.RFC2223">RFC 2223</xref>.
then the XML application inserts an appropriate designation during processing, such as "RFC 2223[2]" or "RFC 2223". Although the XML application decides what "an appropriate designation" might be, its choice is consistent throughout the processing of the document.
The "eref" element is used to reference external documents. The mandatory "target" attribute is a URI[4], e.g.,
<eref target="http://metalab.unc.edu/xml/">Cafe con Leche</eref>
Note that while the "target" attribute is always present, the "eref" element may be empty, e.g.,
<eref target="http://invisible.net/" />
and the XML application inserts an appropriate designation during processing such as "[9]" or "http://invisible.net/".
The "iref" element is used to add information to an index. The mandatory "item" attribute is the primary key the information is stored under, whilst the optional "subitem" attribute is the secondary key, e.g.,
<iref item="indexing" subitem="how to" />
Finally, note that the "iref" element is always empty -- it never contains any text.
The "vspace" element, which may occur only inside the "t" element, is used by the author to provide formatting guidance to the XML application. There is an attribute, "blankLines", that indicates the number of blank lines that should be inserted. A physical linebreak is specified by using the default value, "0".
In addition, the "vspace" element can be used to force a new physical paragraph within a list item, e.g.,
<list style="numbers"> <t>This is list item. <vspace blankLines="1" /> This is part of the same list item, although when displayed, it appears as a separate physical paragraph.</t> </list>
An XML application producing a text version of the document should exercise care when encountering a value for "blankLines" that causes a pagebreak -- in particular, if a "vspace" element causes a pagebreak, then no further blank lines should be inserted. This allows authors to "force" a pagebreak by using an arbitrarily large value, e.g., "blankLines='100'".
Finally, note that the "vspace" element is always empty -- it never contains any text.
Finally, the "back" element is used for references and appendices:
... </middle> <back> <references> <reference ...> <reference ...> </references>

 </back> </rfc>
The "back" element consists of an optional "references" element, and, one or more optional "section" elements. The "back" element itself is optional, if your document doesn't have any references or appendices, you don't have to include it.
The "references" element contains the document's bibliography. It contains one or more "reference" elements.
Each "reference" element contains a "front" element and one or more optional "seriesInfo" elements.
We've already discussed the "front" element back in Front matter.
The "seriesInfo" element has two attributes, "name" and "value" that identify the document series and series entry, respectively.
The "reference" element has an optional "anchor" attribute that is used for cross-referencing with the "xref" element, e.g.,
<reference anchor="refs.RFC2200"> <front> <title>Internet Official Protocol Standards</title> <author initials="J." surname="Postel" fullname="Jon Postel"> <organization abbrev="ISI"> USC/Information Sciences Institute </organization> </author> <date month="June" year="1997" /> </front> <seriesInfo name="RFC" value="2200" /> <seriesInfo name="STD" value="1" /> </reference>
The "reference" element also has an optional "target" attribute that is used for external references (c.f., The eref Element). The XML application, if producing an HTML version of the document will use the "target" attribute accordingly; however, if the "name" attribute of the "seriesInfo" element has the value "RFC", then the XML application should automatically provide an appropriate default for the "target" attribute (e.g., "http://example.com/rfcs/rfc2200.txt").
To include appendices after the bibliography, simply add more "section" elements. (For an example, look at the example at the beginning of Back matter.)
The copyright status for the document is not included in the document's markup -- this is automatically inserted by an XML application that produces either a text or HTML version of the document.
| TOC |
This section concerns itself with applications that operate on an XML source file. A lot of XML tools are available, as are many lists of XML resources, e.g., Cafe con Leche.
There are two kinds of XML tools: validating and non-validating. Both check that the source file conforms to the rules given in XML basics. However, in addition to making sure that the source file is well-formed, a validating tool also reads the DTD referenced by the source file to make sure that they match. There are a number of both validating and non-validating tools available.
There are several XML editors available. Ideally, you want an editor that validates. This has two advantages:
There are two major modes in Emacs that support XML: tdtd and psgml. The latter mode allows you to validate the source file (by calling an external program). If you visit the source file in Emacs and the major mode isn't "SGML" or "XML", then usually all it takes is adding these lines to your ".emacs" file:
(setq auto-mode-alist (cons (cons "\\.xml$" 'sgml-mode) auto-mode-alist))
and then restarting Emacs. If this doesn't work, try one of the sources above.
The author uses both sgml-mode in Emacs, and a commercial validating editor, Clip! version 1.5, when editing source files.
If your editor doesn't validate, then you should run a program to validate the source file.
The author uses the AlphaWorks XML parser for this purpose. It requires that your system have a Java virtual machine. In addition to Java, there are validating parsers written in C, Perl, Python, and Tcl.
The author has written the xml2rfc tool, which reads the source file and produces both a text and HTML version of the document. (This memo was produced using the xml2rfc tool.) Note that xml2rfc isn't a validating tool, so it's a good idea to use either a validating editor or run a stand-alone validating parser prior to using the tool.
The XML Style Language (XSL) is used to describe transformations from the source file into some other structured file. So, ideally you should use an XSL-capable formatter to convert an XML source file to HTML.
However, as of this writing XSL is still in considerable flux. (Hence, no reference was included in this memo, as by the time you read this section, the reference would be outdated.) So, in the interim, the author uses the xml2rfc tool for this purpose, even though this tool doesn't provide much flexibility in its HTML layout.
Browsers that support either XSL or Cascading Style Sheets (CSS) are able to view the source file directly.
At present, the author doesn't use any of these browsers, instead converting source files to either text or HTML.
As with text editors, any text-oriented search tool (e.g., grep) can be used on the source file. However, there are search tools available that understand structured source.
The author uses sgrep version 1.9 for this purpose, e.g.
sgrep -g xml 'ELEMENTS("title") not in ELEMENTS("back")' \ writing-rfcs.xml
which extracts the title element from the source file.
| TOC |
This memo raises no security issues; however, according to [2], your document should contain a section near the end that discusses the security considerations of the protocol or procedures that are the main topic of your document, e.g.,
<middle> ...
 <t>This memo raises no security issues; however, according to <xref target="refs.RFC2223" />, your document should contain a section near the end that discusses the security considerations of the protocol or procedures that are the main topic of your document.</t>
 </middle>
| TOC |
| [1] | World Wide Web Consortium, "Extensible Markup Language (XML) 1.0", W3C XML, February 1998. |
| [2] | Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 2223, October 1997. |
| [3] | Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2026, BCP 9, October 1996. |
| [4] | Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. |
| TOC |
| Marshall T. Rose | |
| Invisible Worlds, Inc. | |
| 660 York Street | |
| San Francisco, CA 94110 | |
| US | |
| Phone: | +1<PHONE_NUMBER> |
| EMail: |<EMAIL_ADDRESS>|
| URI: | http://invisible.net/ |
| TOC |
The "<rfc>" tag at the beginning of the file, with only an "ipr" attribute, produces an Internet-Draft. However, when other attributes are added to this tag by the RFC editor, an RFC is produced, e.g.,
<rfc number="2200" obsoletes="2000, 1920, 1880, 1800, ..." category="std" seriesNo="1">
At a minimum, the "number" attribute should be present.
The other attributes are:
Finally, a special entity, "&rfc.number;", is available. Authors preparing an RFC should use this entity whenever they want to reference the number of the RFC within the document itself. In printed versions of the document, the appropriate substitution (or "XXXX") will occur.
| TOC |
   <!ENTITY % NUMBER "CDATA"> <!ENTITY % NUMBERS "CDATA"> <!ENTITY % DAY "CDATA"> <!ENTITY % MONTH "CDATA"> <!ENTITY % YEAR "CDATA"> <!ENTITY % URI "CDATA"> <!ENTITY % ATEXT "CDATA"> <!ENTITY % CTEXT "#PCDATA"> <!ENTITY % TEXT "#PCDATA"> <!ENTITY rfc.number "2629">   <!ELEMENT rfc (front,middle,back?)> <!ATTLIST rfc number %NUMBER; #IMPLIED obsoletes %NUMBERS; "" updates %NUMBERS; "" category (std|bcp|info|exp|historic) "info" seriesNo %NUMBER; #IMPLIED ipr (full2026|noDerivativeWorks2026|none) #IMPLIED docName %ATEXT; #IMPLIED>  <!ELEMENT front (title,author+,date,area*,workgroup*,keyword*, abstract?,note*)>  <!ELEMENT title (%CTEXT;)> <!ATTLIST title abbrev %ATEXT; #IMPLIED> <!ELEMENT author (organization,address?)> <!ATTLIST author initials %ATEXT; #IMPLIED surname %ATEXT; #IMPLIED fullname %ATEXT; #IMPLIED> <!ELEMENT organization (%CTEXT;)> <!ATTLIST organization abbrev %ATEXT; #IMPLIED> <!ELEMENT address (postal?,phone?,facsimile?,email?,uri?)>  <!ELEMENT postal (street+,(city|region|code|country)*)> <!ELEMENT street (%CTEXT;)> <!ELEMENT city (%CTEXT;)> <!ELEMENT region (%CTEXT;)> <!ELEMENT code (%CTEXT;)> <!ELEMENT country (%CTEXT;)> <!ELEMENT phone (%CTEXT;)> <!ELEMENT facsimile (%CTEXT;)> <!ELEMENT email (%CTEXT;)> <!ELEMENT uri (%CTEXT;)> <!ELEMENT date EMPTY> <!ATTLIST date day %DAY; #IMPLIED month %MONTH; #REQUIRED year %YEAR; #REQUIRED>  <!ELEMENT area (%CTEXT;)> <!ELEMENT workgroup (%CTEXT;)> <!ELEMENT keyword (%CTEXT;)> <!ELEMENT abstract (t)+> <!ELEMENT note (t)+> <!ATTLIST note title %ATEXT; #REQUIRED>  <!ELEMENT middle (section)+> <!ELEMENT section (t|figure|section)*> <!ATTLIST section anchor ID #IMPLIED title %ATEXT; #REQUIRED> <!ELEMENT t (%TEXT;|list|figure|xref|eref|iref|vspace)*> <!ATTLIST t hangText %ATEXT; #IMPLIED>  <!ELEMENT list (t+)> <!ATTLIST list style (numbers|symbols|hanging|empty) "empty"> <!ELEMENT xref (%CTEXT;)> <!ATTLIST xref target IDREF #REQUIRED pageno (true|false) "false"> <!ELEMENT eref (%CTEXT;)> <!ATTLIST eref target %URI; #REQUIRED> <!ELEMENT iref EMPTY> <!ATTLIST iref item %ATEXT; #REQUIRED subitem %ATEXT; ""> <!ELEMENT vspace EMPTY> <!ATTLIST vspace blankLines %NUMBER; "0"> <!ELEMENT figure (preamble?,artwork,postamble?)> <!ATTLIST figure anchor ID #IMPLIED title %ATEXT; ""> <!ELEMENT preamble (%TEXT;|xref|eref|iref)*> <!ELEMENT artwork (%TEXT;)*> <!ATTLIST artwork xml:space (default|preserve) "preserve"> <!ELEMENT postamble (%TEXT;|xref|eref|iref)*>   <!ELEMENT back (references?,section*)> <!ELEMENT references (reference+)> <!ELEMENT reference (front,seriesInfo*)> <!ATTLIST reference anchor ID #IMPLIED target %URI; #IMPLIED> <!ELEMENT seriesInfo EMPTY> <!ATTLIST seriesInfo name %ATEXT; #REQUIRED value %ATEXT; #REQUIRED>
| TOC |
The author gratefully acknowledges the contributions of: Alan Barrett, Brad Burdick, Brian Carpenter, Steve Deering, Patrik Faltstrom, Jim Gettys, Carl Malamud, Chris Newman, Kurt Starsinic, and, Frank Strauss.
| TOC |
| I | |
| indexing | |
| how to |
| TOC |
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

Funding for the RFC Editor function is currently provided by the Internet Society.


Hong Kong families oppose tear gas use on eve of local elections
Dozens of Hong Kong families with young children have chanted “no more tear gas” as they marched to oppose the government’s handling of pro-democracy protests, on the eve of keenly contested local elections.
Riot police have reportedly fired more than 9,000 rounds of tear gas since protests began in June, often in crowded areas and also near schools.
With police now buying canisters from China, there are rising fears that the tear gas could release toxic chemicals including cancer-causing dioxin.
A local journalist covering the protests reportedly said he had been diagnosed with a skin condition linked to exposure to toxins including dioxin.
The government of the Chinese territory this week said there was no evidence of any health or environment risks and has refused to reveal the chemicals in the tear gas, citing operational concerns.
Sunday’s district council have emerged as a pivotal bellwether on public support for the increasingly violent protests, which have disrupted life in the financial hub for months.
There was a rare easing in violence this week as protesters, anxious to validate their cause through the ballot box, paused to ensure the polls would not be postponed.
Online messages have urged protesters not to wear black or face masks during voting in case they are targeted by police.
For the first time, all 452 seats in 18 district councils — currently dominated by pro-establishment parties — are being contested.
Hong Kong chief secretary Matthew Cheung said on Saturday that the vote by nearly 60% of the city’s population is a “real democratic exercise”, and a strong police presence at polling stations will ensure that it proceeds smoothly.


In the case of F0(𝜀,μ,α,X) being isotropic (∂F0∕∂μ = 0 and ∂F0∕∂α = 0 in guiding-center coordinates), Frieman-Chen’s gyrokinetic equation (127) is written as
where δG0 is the gyro-phase independent part of the perturbed distribution δF, and is related to δF by|
| (143) |
where the ﬁrst term is called “the adiabatic term”, which depends on gyro-phase α via δΦ. In Eq. (142), δL = δΦ − v ⋅ δA.
Note that the coeﬃcient before ∂F0∕∂𝜀 in Eq. (142) involves the time derivative of ⟨δϕ⟩α, which is problematic if treated by using explicit ﬁnite diﬀerence in particle simulations (I test the algorithm that treats this term by implicit scheme, the result roughly agrees with the standard method discussed in Sec. 7). It turns out that ∂⟨δΦ⟩α∕∂t can be eliminated by deﬁning another gyro-phase independent function δf by
|
| (144) |
Then, in terms of δf, the perturbed distribution function δF is written as
|
| (145) |
Using Eq. (144) and Eq. (142), the equation for δf is written as
The blue term in expression (145) gives “the polarization density” when integrated in the velocity space (discussed in Sec. 7). The reason for the name “polarization” is that (δΦ −⟨δΦ⟩α) is the diﬀerence between the local value and the averaged value on a gyro-ring, expressing a kind of “separation”.
Similar to the method of eliminating ∂⟨δϕ⟩α∕∂t, we deﬁne another gyro-phase independent function δh by
|
| (148) |
then Eq. (147) is written in terms of δh as
Most gyrokinetic simulations approximate the vector potential as δA ≈ δA∥e∥. Let us simplify Eq. (151) for this case. Then ⟨v ⋅ δA⟩α is written as
|
| (153) |
Note that in terms of (X,𝜀,μ,α,σ) coordinates, v∥ is written as
|
| (154) |
where B0(x) = B0(X + ρ) with ρ = ρ(X,𝜀,μ,α). Since the scale length of B0 is much larger than the thermal Larmor radius, B0(x) ≈ B0(X) and hence v∥ of thermal particles can be approximately considered to be independent of the gyro-angle α. Then v∥ can be taken out of the gyro-averaging in expression (153), yielding
|
| (155) |
Using this, the term related to δA in (151) is written as
In simulations, I use Eq. (158) and set δA∥ to zero to get the electrostatic version, rather than using Eq. (147) as the electrostatic version (the latter contains a nonlinear term on the right-hand side, which seems strange.)
In the above, the perturbed part of the distribution function, δF, is split at least three times in order to (1) simplify the gyrokinetic equation by splitting out the adiabatic response and (2) eliminate the time derivatives, ∂δϕ∕∂t and (3) ∂δA∕∂t, on the right-hand. To avoid confusion, I summarize the split of the distribution function here. The total distribution function F is split as
|
| (159) |
where F0 is the equilibrium distribution function and δF is the perturbed part of the total distribution function. δF is further split as
|
| (160) |
where δh satisﬁes the gyrokinetic equation (151) or (158). In Eq. (160), the red term gives rise to the so-called polarization density (discussed in Sec. 7), which explicitly depends on δΦ. This term is moved to the left-hand side of the Poisson equation and is utilized in solving the Poisson equation. The blue term also has an explicit dependence on δA, which, however, will cause numerical problems in particle simulations if it is moved to the left-hand side of the Ampere equation, giving rise to the so-called “cancellation problem” in gyrokinetic simulations.
Consider the approximation δA ≈ δA∥e∥, then the blue term in Eq. (160) is written as
|
| (161) |
Notice that v∥ can be taken out of the gyro-averaging. Then the above equation is written
|
| (162) |
If we neglect the FLR eﬀect, then the above expression is written
|
| (163) |
The zeroth order moment (number density) is then written as
|
| (164) |
which is zero if F0 is Maxwellian. Next, consider the parallel current carried by distribution (163), which is written
|
| (165) |
If F0 is a Maxwellian distribution given by
|
| (166) |
then
|
| (167) |
Then expression (165) is written
|
| (168) |
Working in the spherical coordinates, then v∥ = v cos𝜃 and dv = v2 sin𝜃dvd𝜃dϕ. Then expression (168) is written
|
| (171) |
The parallel currents are given by
|
| (172) |
|
| (173) |
where δJ∥i′ and δJ∥e′ is the parallel current carried by the distribution function δh in Eq. (160), which are updated from the value at the nth time step to the (n + 1)th time step using an explicit scheme and therefore does not depends on the ﬁeld at the (n + 1)th step. The blue terms in Eqs. (172) and (173) depend on the unknown ﬁeld at the (n + 1)th step and thus need to be moved to the left-hand side of Ampere’s law (171) if we want to solve this equation by direct methods. In this case, equation (171) is written as
Therefore we go back to Eq. (171) and try to solve it using iterative methods. However, it is found numerically that directly using Eq. (171) as an iterative scheme is usually divergent. To obtain a convergent iterative scheme, we need to have an approximate form for the blue terms, which is independent of markers and so that it is easy to construct its matrix, and then subtract this approximate form from both sides. After doing this, the iterative scheme has better chance to be convergent. An approximate form is that derived by neglecting the FLR eﬀect given in Sec. 5.4. Using this, the iterative scheme for solving Eq. (171) is written as
In the drift-kinetic limit (i.e., neglecting the FLR eﬀect), the blue and red terms on the right-hand side of the above equation cancel each other exactly. Even in this case, it is found numerically that these terms need to be retained and the blue terms are evaluated using markers. Otherwise, numerical inaccuracy can give numerical instabilities, which is the so-called cancellation problem. The explanation for this is as follows. The blue terms are part of the current. The remained part of the current carried by δh is computed by using Monte-Carlo integration over markers. If the blue terms are evaluated analytically, rather than using Monte-Carlo integration over markers, then the cancellation between this analytical part and Monte-Carlo part can have large error (assume that there are two large contribution that have opposite signs in the two parts) because the two parts are evaluated using diﬀerent methods and thus have diﬀerent accuracy, which makes the cancellation less accurate.The blue terms are sometimes called “adiabatic current”. The red terms are approximation to the “adiabatic current” obtained by neglecting the FLR eﬀect. Because the ion adiabatic current is less than the electron adiabatic current by a factor of me∕mi, its accuracy is not important, and is approximated by the drift-kinetic limit in GEM. And the cancellation error is not a problem and hence can be neglected. In this case, equation (175) is simpliﬁed as
The perturbed distribution function is decomposed as given by Eq. (160), i.e.,
|
| (177) |
where the term in blue is the so-called adiabatic response, which depends on the gyro-angle. Recall that the red term ⟨δΦ⟩α, which is independent of the gyro-angle, is introduced in order to eliminate the time derivative ∂⟨δΦ⟩α∕∂t term on the right-hand side of the original Frieman-Chen gyrokinetic equation.
The so-called generalized split-weight scheme corresponds to going back to the original Frieman-Chen gyrokinetic equation by introducing another ⟨δΦ⟩α term with a free small parameter 𝜖g. Speciﬁcally, δh in the above is split as
|
| (178) |
(If 𝜀g = 1, then the two ⟨δΦ⟩α terms in Eq. (177) and (178) cancel each other.) Substituting this expression into Eq. (152), we obtain the following equation for δhs:
Noting that ∂F0∕∂t = 0, e∥⋅∇F0 = 0, ∇F0 ∼ O(λ1)F0, we ﬁnd that the third line of the above equation is of order O(λ3) and thus can be dropped. Moving the second line to the right-hand side, the above equation is written as
For the special case of 𝜖g = 1 (the default and most used case in GEM code, Yang Chen said 𝜖g < 1 cases are sometimes not accurate, so he gave up using it since 2009), equation (180) can be simpliﬁed as:
where two VG ⋅⟨δΦ⟩α terms cancel each other. Because the v∥E∥ term is one of the factors that make kinetic electron simulations diﬃcult, eliminating VG ⋅⟨δΦ⟩α term may be beneﬁcial for obtaining stable algorithms.For 𝜖g = 1, δF is written as
Equation (181) actually goes back to the original Frieman-Chen equation. The only diﬀerence is that ⟨v ⋅δA⟩α is further split from the perturbed distribution function. Considering this, equation (181) can also be obtained from the original Frieman-Chen equation (142) by writing δG0 as
|
| (183) |
In this case, δF is written as
|
| (184) |
Substituting expression (183) into equation (142), we obtain the following equation for δhs:
Noting that ∂F0∕∂t = 0, e∥⋅∇F0 = 0, ∇F0 ∼ O(λ1)F0, we ﬁnd that the third line of the above equation is of order O(λ3) and thus can be dropped. Moving the second line to the right-hand side, the above equation is written as which agrees with Eq. (181).In GEM, the split weight method is used only for electrons and the ∂⟨δΦ⟩α∕∂t is approximated by ∂δΦ∕∂t and this term is obtained from the vorticity equation (rather than from an implicit iteration).
In particle simulations, the seemingly trivial thing on how to split the distribution function is often considered to be a big deal. Separating the perturbed part from the equilibrium part is considered to be a big deal and got the famous name “δf particle method”, in contrast to the conventional particle method which is now called full-f particle method. Summarizing the above result, the total distribution function F is split in the following form:


-
I loved this book, mainly for the extremely candid stories of the early days of startups. Most histories of "the early days" miss out these completely-winging-it and personal-strife aspects...
-
"money that feels different when you’re down to your last ten Euro note"
-
"For people living in the real world, having a great network connection at all times day or night is a non-starter the minute the airplane door closes to fly you to your next destination."
-
-
"...a service that will let utilities such as power and phone companies send reminders to customers via text message, giving them an opportunity to pay their bills before they lose prompt payment discounts or face other sanctions"
-
"If a major project is truly innovative, you cannot possibly know its exact cost and its exact schedule at the beginning. And if in fact you do know the exact cost and the exact schedule, chances are that the technology is obsolete.'' Lovely :)
-
-
Permissions keep popping up in apps we're working on. They're a difficult place to balance flexibility and ease-of-use...
-
-


Association of Road Racing Statisticians
Goals
To establish valid criteria for road record-keeping and to maintain a valid list of world road records for the standard road distances.
To promote communication and the exchange of information with regards to road racing.
Founding Members (alphabetically by country, then by family name)
David Blaikie (CAN<EMAIL_ADDRESS>Ian Champion (ENG<EMAIL_ADDRESS>Andy Milroy (ENG<EMAIL_ADDRESS>Luis Arribas Sandonis (ESP<EMAIL_ADDRESS>Indro Neri (ITA<EMAIL_ADDRESS>Ken Nakamura (JPN<EMAIL_ADDRESS>Gunars Akerbergs (LAT, deceased)
Wim vanHemert (NED<EMAIL_ADDRESS>Zbigniew Jonik (POL<EMAIL_ADDRESS>Riel Hauman (RSA<EMAIL_ADDRESS>Sergey Krashnoshchekov (RUS<EMAIL_ADDRESS>Juraj Gasparovic (SVK<EMAIL_ADDRESS>Tomas Magnusson (SUI<EMAIL_ADDRESS>Birger Fält (SWE<EMAIL_ADDRESS>Pete Riegel (USA, deceased)
Ken Young (USA, deceased)
ARRS Co-ordinator
Andy Milroy<EMAIL_ADDRESS>serves to help co-ordinate the activities of the various members, facillitate internal communication, and interface with organizations outside the ARRS. This is in addition to his passion for developing a historical record of distance running in the 19th and earlier centuries.
ARRS Members
Anyone interested in supporting and promoting the goals of the ARRS is welcome to become a member. The only requirement for membership is that you contribute to the ARRS in some manner. This may be by submitting race results, contributing to the various lists maintained by the ARRS, promoting the goals of the ARRS through articles and publications, or helping with some of the many day-to-day tasks in making the ARRS a viable organization. Contact the ARRS co-ordinator, Andy Milroy if you wish to join the ARRS. Races as well as individuals may become members of the ARRS.
Last Updated on
12 May 2018


| CONTENTS | PREV | NEXT |
Appendix B:
This appendix contains sample JNDI programs intended to help a developer familiar with the LDAP C API. Starting with sample programs from the Netscape Directory SDK for accessing and updating the directory using the LDAP C API, we show the equivalent way of doing the same thing for Java applications using JNDI.


We are here to make you build the website
Website Builder makes it simple to create a modern, professional site with no technical knowledge required.
- Whatever you choose, you're on your way to a brilliant website. .
10
Clients
5
Projects
Contact
We are here to help you, and make your experience worth it.
Our Address
MIT-WPU, Rambaug Colony, Kothrud, Pune, Maharashtra, India
Email Us
<EMAIL_ADDRESS>Call Us
+9118001800
"


Genesis 42:30
The man, who is the lord of the land, spake roughly to us, and took us for spies of the country.


--- permalink: /404.html ---
Unfortunately, this page does not exist. Please check your URL or use the navigation below.


Activity feeds
@{{ status.screen_name }} - {{ status.status.created_at | tweetFromNow }}
The user you're searching for doesn't seem to have location enabled!


5 Images and Poems
All that glows sees
Yes baby, I know it’s hard
Illusion is everything
and it holds you
The song you sang
No satisfaction
All you need is
A room
Illusion is everything
and it holds you
The song you sang
No satisfaction
All you need is
A room
Kara Lease
What a feeling
I don’t believe in mystery
never saw it happen
happening
A softly spoken magic spell
-
There is a god
When I first met you
My life was empty
My life is real
But it is only a fantasy
I’d like to be there
But I can’t
I don’t believe in mystery
never saw it happen
happening
A softly spoken magic spell
-
There is a god
When I first met you
My life was empty
My life is real
But it is only a fantasy
I’d like to be there
But I can’t
The Angelic Organic
I feel safest in knowing that I am true
When this is
That is
When this isn’t
That isn’t
Body inside of time
To become an enlightened being
Or to conquer the world
Head Map
Takes lots of pictures
Everything coming together
Not knowing anyone
Never closed
open
Veracity
In a fabric of knowing
In a fabric of
Fabric
Knowing
Intentions of actions
Intentions of forces
An angelic organic
When this is
That is
When this isn’t
That isn’t
Body inside of time
To become an enlightened being
Or to conquer the world
Head Map
Takes lots of pictures
Everything coming together
Not knowing anyone
Never closed
open
Veracity
In a fabric of knowing
In a fabric of
Fabric
Knowing
Intentions of actions
Intentions of forces
An angelic organic


Introduction to Sendmail
Sendmail is the standard Unix program for mail transport and delivery.
When a user on your system wants to send email to someone on another host,
sendmail is the program that does the actual process of delivering the
mail. Similarly, when someone on another system sends mail to one of your
users, sendmail will receive the email and store it in the user's mail
file.
Sendmail is an MTA (mail transport agent) only, meaning that it does not
present any user interface to people wishing to send email. Programs like
Eudora, elm or /bin/mail that users actually interact with a called MUAs
(mail user agents). An MUA does not deliver email itself, instead it simply
passes the email on to sendmail to do the delivery.
User MUAs can be run either directly on your system (MUAs like pine, elm
or /bin/mail), or on a separate host which may be a single-user PC (for MUAs
like Eudora, Exchange and Netscape Communicator). In the first case,
mail is sent be directly invoking sendmail and passing the message to it,
and received by reading the user's mail spool file. For MUAs run on other
hosts, mail is sent by connecting to the sendmail process on your system
using the SMTP protocol, and received by connecting to a separate POP3
server.
The Sendmail Module
The main page of this module shows a table of icons, each for configuring
a different part of sendmail's functionality. However, the features behind
some icons may not be available, if they have not been setup in your
sendmail.cf. When installing sendmail, you can choose which features
are available by editing an .mc, which is converted by m4
into your sendmail.cf. Many features (such as Address Mapping,
Domain Masquerading and Spam Control) may not be available unless you have
enabled them at install time.


The HACL and EverCrypt reference manual¶
This manual describes the HACL*, Vale and EverCrypt formally verified cryptographic libraries.
Parts of these libraries appear in Firefox, the Windows kernel, the Linux kernel, the Tezos blockchain, the Microsoft MSQuic implementation of the QUIC protocol, and the Wireguard VPN.
HACL* provides a set of highly efficient, pure C implementations of complete cryptographic primitives. Each algorithm comes with its own API callable from C clients.
Vale provides optimized assembly (ASM) core routines for performance-critical code. Vale code is not intended to be called from C by end users.
EverCrypt brings HACL* and Vale under an abstract, high-level API that automatically picks the best Vale or HACL* implementation depending on the machine the code is running on (multiplexing). EverCrypt also offers a single API for all algorithms from the same family (e.g. AEAD, hashes), allowing clients to reconfigure their choice of algorithm dynamically without recompiling (agility).
All of our code is verified using the F* programming language; once verified, our code is extracted to a mixture of C and ASM.
Our code is callable from C clients, and from OCaml, via ctypes bindings. A subset of our code (the HACL API) compiles to WebAssembly via a dedicated, formalized codepath of the KreMLin compiler and can be used for any Web context (e.g. Electron, website) where modern, trustworthy cryptography is in order.
In addition to unverified clients, verified clients can be built atop the EverCrypt API. These include a library of Merkle Trees, distributed in the present repository, but also an implementation of the Signal protocol in F*.
- List of supported algorithms
- The research behind
- Obtaining the source code
- General recommendations
- HACL APIs
- EverCrypt APIs
- CPU autodetection (
EverCrypt_AutoConfig2.h
) - AEAD (
EverCrypt_AEAD.h
) - CTR-mode encryption (
EverCrypt_CTR.h
) - Hashing (
EverCrypt_Hash.h
) - HMAC (
EverCrypt_HMAC.h
) - HKDF (
EverCrypt_HKDF.h
) - HMAC-DRBG (
EverCrypt_DRBG.h
) - Deprecated block cipher API (
EverCrypt_Cipher.h
) - Legacy EverCrypt headers (
EverCrypt.h
,EverCrypt_Hacl.h
,EverCrypt_Vale.h
)
- CPU autodetection (
- Merkle Tree API
- WebAssembly bindings
- OCaml bindings


http://action.vday.org/site/R?i=YD6Q2_mOuLrE1Xx8p7jE4w
http://action.vday.org/site/R?i=kQnarzzQCemhxf1UPXw36w
http://action.vday.org/site/R?i=Dnr98C1rvHx0V5qv7GY0AQ
http://action.vday.org/site/R?i=HnDnC4SslYQ7JwyoN5NDwg
WATCH ONLINE TONIGHT:
Breaking The Male Code: After Steubenville, A Call To Action
Tonight at 7:30pm ET, WATCH ONLINE the sold out, one night only panel
discussion Breaking The Male Code: After Steubenville, A Call To
Action. Presented by V-Day and The Nation, this powerful and timely
discussion will feature Journalist and Teacher Jimmie Briggs,
President of Coach for America and former football player Joe Ehrmann,
A Call to Men Co-Founder Tony Porter, and Sports Editor at The Nation
Dave Zirin, with a special introduction by Emmy Award-winning musician
and Co-Chair of the NoVo Foundation Peter Buffett, and moderated by
Eve Ensler.
WATCH ONLINE at www.vday.org/livestream
http://action.vday.org/site/R?i=YxabdgcqnfYT4uoXY1gFcA
LEARN more about the panelists >
http://action.vday.org/site/R?i=XoeVfvXs97qsWBjy8Do7Dw
http://action.vday.org/site/R?i=FaTK_aTwaT2L64SEaLMPWA
http://action.vday.org/site/R?i=ID-ZSZ8WWoHe8D9GsGj85g
http://action.vday.org/site/R?i=6hw_v43vGtLMxvbB5IQTmA
http://action.vday.org/site/R?i=oEdcOGpyEhBNMAj_KQKNLg
http://action.vday.org/site/R?i=BrXcdBNaJxps1boDoL9RYQ
unsubscribe
http://action.vday.org/site/CO?i=KW1YSi0WqP5ICriLFvT0bYeacKc–_zf&cid=1062
Powered By Convio


Open User Font Section User's Font Family Family List Font Size in PX units Letter Spacing in EM units above normal Word Spacing in EM units above normal Close User Fonts Open Author Font Section Author Font Family Family List Font Size PX units Letter Spacing in EM units above normal Word Spacing in EM units above normal Close the Author Font Close Font Settings


{% extends "base.html" %} {% block title %}Page not found{% endblock %} {% block content %}
Are you sure you're in the right place? Because unless you wanted to see this message, you're probably not.


Pirate (ARRR) is a cryptocurrency that solves the issue of financial privacy on the blockchain through forced anonymous transactions. Protect your wallet and transactions with Pirate’s completely anonymous network. With forced private transactions, your privacy cannot be compromised by another users’ activity on the network. If you wish to learn more, please join the official Pirate Discord at https://pirate.black/discord/ or message FishyGuts#5085, who will be happy to help out.
100 messages
Before 05-Dec-19 12:00 AM
CryptoFoxGaming11-Sep-18 02:54 AM
Also, your view key isn;t long enough.
It should look like this: "ZiVKe1SKhNjv2ewZXMDMnzzRwEKkna3hJoMXtwPoTcdQY61MKc3f8HWaavqDLtjEunk6ydR765T7bsPHA6rkBLYmeNgcwvbwL"
Or you could give me a real viewing key to play with.
Here is the import command: z_importviewingkey
Well... what are you waiting for? I could empty it out and try again but that wouldn't prove it.
It is KMD. Should be empty.
I just quickly ran komodod with default settings and brought up the cli.
Alright11-Sep-18 03:04 AM
nou
woah my staked KMD node forked?
or is rejecting blocks
well no, I just realized because I tried to run that
CryptoFoxGaming11-Sep-18 03:06 AM
So, any luck?
Also, the whenkeyisnew is optional.
1
It doesn't have any TX associated with it so I don't see the point of a rescan.(edited)
komodo-cli z_importviewingkey "ZiVKe1SKhNjv2ewZXMDMnzzRwEKkna3hJoMXtwPoTcdQY61MKc3f8HWaavqDLtjEunk6ydR765T7bsPHA6rkBLYmeNgcwvbwL" no
1
Rescan from 0 is default, this should prevent that.
@Alright, help! I need to prove a point! And I am stubborn so I can't go to sleep yet...
That is the one. I have a snip of my CLI to prove it.
I know KMD is 200_9, but wasn't sure is that meant PIRATE was as well.
CryptoFoxGaming11-Sep-18 04:39 AM
@webworker01, that is a lot of SOLs to just drop. I hop in and out, but I am not even at a ksol/sec. :P
CryptoFoxGaming11-Sep-18 05:11 AM
@webworker01, for me it is just more so because my laptop doubles as a mining rig so when I need to use it for something, I have to switch the mining off. Still 300 Sols/sec isn't too bad.
Also, found out the new EWBF doesn't support the KMD equihash variant.
Yup. They removed them.
Alright11-Sep-18 05:13 AM
should be using PPLNT
CryptoFoxGaming11-Sep-18 05:14 AM
He said he may add it in an update but didn't focus on it because of the ASICS.
Also, IDK about the temp. It runs pretty hot just for gaming.
Lots of people run this particular laptop pretty hot. I have already undervalued the CPU though.
1
kmdkrazy11-Sep-18 05:39 AM
yes we do
bobby trump
later
1
Mylo11-Sep-18 07:53 AM
PPLNT any info on it? and what are the other options when running a mining pool? for a pirate article.
 I just want to make sure I have it close to optimal
Alright11-Sep-18 12:05 PM
~700sols
wookie11-Sep-18 12:06 PM
Thanks. That's what I get ~695-705. What about a 1060 3gb?
Alright11-Sep-18 12:06 PM
no idea
wookie11-Sep-18 12:10 PM
ok. thanks.
Flexatron11-Sep-18 12:14 PM
Difficulty dropped below 2M
5Q and 4T were like, yo lets both spend less money
For the same result
abcd11-Sep-18 12:18 PM
hahaha
4t had 1.2msols yesterday
1080ti can do 740khs, but optimal efficiency is received at 60-75% tdp depending on model
Flexatron11-Sep-18 12:20 PM
Whats the conversion to sol?
abcd11-Sep-18 12:20 PM
Lyrarev2 for example on a evga ftw3 uses 60%, sc2 uses 65% for same power draw and hashrate “roughly”
Sorry 740 sols
Flexatron11-Sep-18 12:21 PM
Khs = sols?
abcd11-Sep-18 12:21 PM
Which is 740hs I believe
Flexatron11-Sep-18 12:21 PM
Ah
abcd11-Sep-18 12:21 PM
0.74khs
You have 1080ti mining?
You don’t want to mine equihash if that’s the case.
Get the software bios mod for 1080ti and ethhash becomes 40% more profitable?
Even then, I think lyrarev2 is slightly more profitable than ethhash
wookie11-Sep-18 12:27 PM
if electricity is not a cost, would you still recommend ethhash?
I can't get my 1080ti to 740. I'm at 100% power, 69-70degrees, -15core, +820memory
blackjok3r11-Sep-18 12:32 PM
WTS 300k PIRATE
CHMEX11-Sep-18 12:34 PM
how much?
Don King11-Sep-18 12:39 PM
Yeah, how much for 300k?
jorian11-Sep-18 12:40 PM
1 KMD for 300k PIRATE. who bids higher
Decker11-Sep-18 12:41 PM
2 KMD. Somebody else ? ))
CHMEX11-Sep-18 12:42 PM
I do 80 KMD for 300k
jorian11-Sep-18 12:42 PM
wow, moon
Decker11-Sep-18 12:43 PM
jorian11-Sep-18 12:43 PM
last going price was 0.003 afaik
Decker11-Sep-18 12:44 PM
I think reasonable price is something near 1000 KMD for 250k PIRATES ...
blackjok3r11-Sep-18 12:44 PM
0.00375 or something I was offered but was too busy to sell a few days back. Not sure where that pereson went.(edited)
Alright11-Sep-18 12:44 PM
@Decker deal
jorian11-Sep-18 12:44 PM
i think it was bobby
Decker11-Sep-18 12:45 PM
@Alright )) I'm a bad buyer ... haven't KMD )
Alright11-Sep-18 12:45 PM
Have a good chunk of PIRATE that I will trade for a good chunk of STAKED
blackjok3r11-Sep-18 12:46 PM
if anyone can figure out how to make it so that we can use 1 constant array fo pubkeys in STAKED komodo repo I will pay 3000 staked bounty.
CHMEX11-Sep-18 12:46 PM
whats is the PIRATE / STAKED price
blackjok3r11-Sep-18 12:46 PM
no idea
CHMEX11-Sep-18 12:47 PM
if somebody wants I buy :
200k PIRATE for 8000 STAKED(edited)
1
Don King11-Sep-18 12:49 PM
I'll buy PIRATE @ 0.0035
Alright11-Sep-18 12:49 PM
total supply of PIRATE atm?
CHMEX11-Sep-18 12:49 PM
4'644'125
Flexatron11-Sep-18 01:15 PM
Ill sell for one dorrah/pirate
wookie11-Sep-18 01:51 PM
wow, 5Q just pumped up to 300k sols...whew!
Flexatron11-Sep-18 01:54 PM
Like everytime
Flexatron11-Sep-18 04:36 PM
Almost at 1/4 of the first emission round
scubapanda11-Sep-18 07:35 PM
Whaaat, what about KMD/Pirate? " Sapling Turnstile
To audit existing shielded ZEC, we’ve implemented a process we call the Sapling turnstile. Users will be required to send funds held in old Sprout shielded addresses to transparent addresses before sending to new Sapling shielded addresses. There will be no way to send ZEC directly between Sprout and Sapling shielded addresses."
I especially like the Pirate part where you are required: "to send funds held in old Sprout shielded addresses to transparent addresses".


{% include meta_tags/base.html %} {% include externals/styling.html %}
{% include header.html %} {{ content }}
{% include externals/scripting.html %}


Using business logic callbacks
XData allows to use business logic callbacks to interact back-end modules with front-end using synchronous Callback and asynchronous PostData models. Synchronous calls can return result value. Callbacks can be used with three-tier-architecture as well as with client-server model. Callbacks has provided business logic clear, complete view and allows debug same code in two-tier environment as code will be executed in three-tier.
public class InvoiceLogic : XDataLogic<Invoice>
{
public CustomLogic<Invoice> TestCustomLogic => (objects => {
Log.Write(MessageType.Information,
() => $"TestCustomLogic called with {objects.Length} objects");
foreach (var invoice in objects)
{
var i = invoice;
invoice.PostData("testPost", () => Encoding.UTF8.GetBytes(i.DocNumb));
var p = Encoding.UTF8.GetBytes(i.DocNumb);
var r = i.Callback("testCall", ref p);
Log.Write(MessageType.Information, () =>
@$"Call for \"{i.DocNumb}\" returned \"{r}\" with data
\"{(p == null ? null : Encoding.UTF8.GetString(p))}\"");
}
return true;
});
}


IS445 Homework and Project
John Tran
Home
About
(current)
Bootstrap
Future
Homework 3
Homework 4
Midterm
Homework 5
Homework 6
Project
"Woof woof woooof, woof woof woof" -dog
About Me
Education and Skills
Education
2018, Information Systems, CSULB
Skills
Python, Oracle


Go to the source code of this file.
Defines | |
| #define | NUM_ELEMENTS 25 |
| #define | TY_ROOT 000000000 |
| #define | TY_TOPLEVEL 000000001 |
| #define | TY_RESOURCE 000000002 |
| #define | TY_FIELD 000000004 |
| #define | TY_PARAM 000000010 |
| #define | TY_INFO 000000020 |
| #define | TY_TR 000000040 |
| #define | TY_TD 000000100 |
| #define | TY_TABLE 000000200 |
| #define | TY_STREAM 000000400 |
| #define | TY_FITS 000001000 |
| #define | TY_GROUP 000002000 |
| #define | TY_FIELDREF 000004000 |
| #define | TY_PARAMREF 000010000 |
| #define | TY_MIN 000020000 |
| #define | TY_MAX 000040000 |
| #define | TY_OPTION 000100000 |
| #define | TY_VALUES 000200000 |
| #define | TY_LINK 000400000 |
| #define | TY_DATA 001000000 |
| #define | TY_DESCRIPTION 002000000 |
| #define | TY_TABLEDATA 004000000 |
| #define | TY_BINARY 010000000 |
| #define | TY_BINARY2 020000000 |
| #define | TY_COOSYS 100000000 |
| #define | TY_DEFINITIONS 200000000 |
| #define | OK 0 |
| #define | ERR 1 |
| #define | TRUE 1 |
| #define | FALSE 0 |
| #define | handle_t int |
Functions | |
| handle_t | xml_openXML (char *arg) |
| Parse an XML document and return a handle to it. | |
| void | xml_closeXML (handle_t vot) |
| Destroy the root node and all of it's children. | |
| handle_t | xml_newNode (handle_t parent, int type) |
| Creates a new blank unlinked node. | |
| void | xml_freeNode (handle_t delete_me) |
| Destroys the node and all of it's children. | |
| void | xml_attachNode (handle_t parent, handle_t new) |
| Adds a node as a child of parent. | |
| void | xml_deleteNode (handle_t element) |
| Destroys the node and all of it's children. | |
| handle_t | xml_copyElement (handle_t src_h, handle_t parent_h) |
| Adds a node as a child of parent. | |
| handle_t | xml_findByAttr (handle_t parent, char *name, char *value) |
| Get a handle to an Element with the requested attribute. | |
| handle_t * | xml_findInGroup (handle_t group, int type) |
| handle_t | xml_getNext (handle_t elem_h) |
| Return a handle_t of the next Element of the same type. | |
| handle_t | xml_getSibling (handle_t elem_h) |
| Return a handle_t of the next Element. | |
| handle_t | xml_getChild (handle_t elem_h) |
| Return a handle_t of the child Element. | |
| handle_t | xml_getParent (handle_t elem_h) |
| Return the handle of the parent Element. | |
| handle_t | xml_getChildOfType (handle_t elem_h, int type) |
| Get the handle of the next Element of the same type. | |
| handle_t | xml_getToplevel (handle_t root) |
| Get the handle to the toplevel element. | |
| int | xml_valueOf (handle_t elem_h) |
| Return type of the Element. | |
| int | xml_typeOf (handle_t elem_h) |
| Return type of the Element. | |
| int | xml_handleCount () |
| Get the number of handle_t used (private method). | |
| char * | xml_elemNameByHandle (handle_t elem) |
| Get the name of requested element. | |
| char * | xml_getToplevelName (handle_t root) |
| Get the name of toplevel element. | |
| char * | xml_getToplevelNSpace (handle_t root) |
| Get the name of toplevel element namespace. | |
| int | xml_setValue (handle_t elem_h, char *value) |
| Set the Value for the ELEMENT. | |
| char * | xml_getValue (handle_t elem_h) |
| Get the Value for the ELEMENT. | |
| int | xml_setAttr (handle_t elem_h, char *attr, char *value) |
| Set the attribute for the Element. | |
| char * | xml_getAttr (handle_t elem_h, char *attr) |
| Return the attribute for the Element. | |
| char * | xml_dumpAllAttr (handle_t elem_h) |
| Dump all information about the attributes of the Element. | |
| char * | xml_dumpNamesAttr (handle_t elem_h) |
| Dump all names of the attributes of the Element. | |
| void | xml_setWarnings (int value) |
| Set the warning level. | |
| void | xmlEmsg (char *msg) |
| void | xml_dumpXMLpublic (handle_t elem_h, int level, int indent, FILE *fd) |
XMLPARSE.H -- Public procedure declarations for the XML parser interface.
8/18/14
| #define NUM_ELEMENTS 25 |
VOTable element types
| void xml_attachNode | ( | handle_t | parent, | |
| handle_t | new | |||
| ) |
| void xml_closeXML | ( | handle_t | xml | ) |
Destroy the root node and all of it's children.
xml_closeXML -- Destroy the root node and all of it's children.
| xml | A handle to the Element that you want deleted |
| handle_t xml_copyElement | ( | handle_t | src_h, | |
| handle_t | parent_h | |||
| ) |
Adds a node as a child of parent.
xml_copyElement -- Adds a node as a child of parent.
| src_h | A handle to the Element to copy | |
| parent_h | A handle to the Elements parent |
| void xml_deleteNode | ( | handle_t | element | ) |
Destroys the node and all of it's children.
xml_deleteNode -- Destroys the node and all of it's children.
| element | A handle to the Element that you want deleted |
| char* xml_dumpAllAttr | ( | handle_t | elem_h | ) |
| char* xml_dumpNamesAttr | ( | handle_t | elem_h | ) |
| char* xml_elemNameByHandle | ( | handle_t | elem | ) |
Get the name of requested element.
xml_elemNameByHandle -- Get the name of requested element.
| elem | element handle |
| handle_t xml_findByAttr | ( | handle_t | parent, | |
| char * | name, | |||
| char * | value | |||
| ) |
| void xml_freeNode | ( | handle_t | node | ) |
Destroys the node and all of it's children.
xml_freeNode -- Destroys the node and all of it's children.
| node | A handle to the Element that you want deleted |
| char* xml_getAttr | ( | handle_t | elem_h, | |
| char * | attr | |||
| ) |
| handle_t xml_getChild | ( | handle_t | elem_h | ) |
| handle_t xml_getChildOfType | ( | handle_t | elem_h, | |
| int | type | |||
| ) |
| handle_t xml_getNext | ( | handle_t | elem_h | ) |
| handle_t xml_getParent | ( | handle_t | elem_h | ) |
| handle_t xml_getSibling | ( | handle_t | elem_h | ) |
| handle_t xml_getToplevel | ( | handle_t | root | ) |
Get the handle to the toplevel element.
xml_getToplevel -- Get the handle to the toplevel element.
| root | document root handle |
| char* xml_getToplevelName | ( | handle_t | root | ) |
Get the name of toplevel element.
xml_getToplevelName -- Get the name of toplevel element.
| root | document root handle |
| char* xml_getToplevelNSpace | ( | handle_t | root | ) |
Get the name of toplevel element namespace.
xml_getToplevelNSpace -- Get the name of toplevel element namespace.
| root | document root handle |
| char* xml_getValue | ( | handle_t | elem_h | ) |
Get the Value for the ELEMENT.
xml_getValue -- Get the Value for the ELEMENT.
| elem_h | A handle_t the ELEMENT |
| int xml_handleCount | ( | ) |
Get the number of handle_t used (private method).
count of current used handles xml_handleCount -- Get the number of handle_t used (private method)
| handle_t xml_newNode | ( | handle_t | parent, | |
| int | type | |||
| ) |
Creates a new blank unlinked node.
xml_newNode -- Creates a new blank unlinked node.
| parent | A handle to the Element that you want to add a node to | |
| type | The type of node you wish to create |
| handle_t xml_openXML | ( | char * | arg | ) |
Parse an XML document and return a handle to it.
************************************************************************* Public LIBVOSI interface.
xml_openXML -- Parse an XML document and return a handle to it
| arg | The source of the table |
********************************************** Create an empty, but valid, DOM tree.
********************************************** Download the URL and process the result.
********************************************** Get the input from stdin.
********************************************** Process a local file URI.
********************************************** Process a local file pathname.
********************************************** Process an input argument is XML string
| int xml_setAttr | ( | handle_t | elem_h, | |
| char * | attr, | |||
| char * | value | |||
| ) |
| int xml_setValue | ( | handle_t | elem_h, | |
| char * | value | |||
| ) |
Set the Value for the ELEMENT.
xml_setValue -- Set the Value for the ELEMENT.
| elem_h | A handle_t the ELEMENT | |
| value | A string holding the value |
| void xml_setWarnings | ( | int | value | ) |
Set the warning level.
xml_setWarnings -- Set the warning level.
| value | Warning level |
| int xml_typeOf | ( | handle_t | elem_h | ) |
| int xml_valueOf | ( | handle_t | elem_h | ) |
| void xmlEmsg | ( | char * | msg | ) |
xmlEmsg -- Error message print utility.


Javascript Barcode Reader
Barcode reader for Browser and Node.js
code
Github
cloud_download
npm
save
Download
Samples
Try these built in samples:
EAN-13 (UPC)
Scan
EAN-8
Scan
Code-39
Scan
Code-93
Scan
Code-2of5 (standard)
Scan
Code-2of5 (interleaved)
Scan
Codabar
Scan
Code-128
Scan
Ready to start?
Get Started Now


{{oDataFilter$ | async}}
You will be searching across every asset in your tenancy
To restrict asset searches to specific assets add assets to the filter from the list above


Stevie Feliciano
Tested in 2014
Stevie Feliciano is a library scientist living in New York City. She likes to spend her time reading, running, and writing.
22 Friends
Stevie Feliciano
Tested in 2014
Stevie Feliciano is a library scientist living in New York City. She likes to spend her time reading, running, and writing.
22 Friends
Stevie Feliciano
Tested in 2014
Stevie Feliciano is a library scientist living in New York City. She likes to spend her time reading, running, and writing.
22 Friends
Stevie Feliciano
Tested in 2014
Stevie Feliciano is a library scientist living in New York City. She likes to spend her time reading, running, and writing.
22 Friends


Neurons Are Like Switches That Are Connected Together
When stimulated, a neuron could be thought as switched on, and it would activate other neutrons in the network. However, unlike switches, the amount of stimulus is related how strong each connections is. The output would be based on the stimulus passing through all these varying strength connections.
How Software Models Neural Network
It uses Math of course! The software would receive a pattern an input, and it would adds up the input’s stimulus effect on each neutron and calculate the output, in a cascaded style.
The software also has to have weights to define the strength of each neuron connection. For backpropagation algorithm specifically, the network is first initialized with random weights. Then the system would start receiving training sets (patterns that we know what they mean) and compare the computed outputs with the known outputs. If any error is found, the error is then fed back through the system to adjust the weights. After thousands or more training sets, all the weights inside the system would be adjusted to an optimal value to produce the correct output. Therefore, the system learned how to properly respond to (interprete) any input patterns.
Example of a 3 layer feed forward network: [Input -> Hidden -> output]. This layout can solve any truth table!!!


template<typename T, typename ... Ts>
StdDataFrame<T>
get_reindexed(const char *col_to_be_index, const char *old_index_name = nullptr) const;
|
It creates and returns a new DataFrame which has the col_to_be_index column as the index. If old_index_name is not null, it will be loaded as a regular column in the result under the name old_index_name.
NOTE: If the new index column is shorter than other columns, every column will be cut to that length.
NOTE: Columns will not be padded by nan
|
T: Type of the "new index" column
Ts: List all the types of all data columns. A type should be specified in the list only once.
col_to_be_index: Name of the column you want as the new index. This name will not be a column in the result anymore
old_index_name: Name of the current index, if converted into a regular column in the result. If this is null, the current index will not be loaded into the result as a column.
|
template<typename T, typename ... Ts>
StdDataFrame<T>
get_reindexed_view(const char *col_to_be_index, const char *old_index_name = nullptr) const;
|
This is similar to get_reindexed(), but it returns a view. Please read above for specs.
Note: There are certain operations that you cannot do with a view. For example, you cannot add/delete columns, etc.
Note: Although this is a const method, it returns a view. So, the data could still be modified through the returned view
|
T: Type of the "new index" column
Ts: List all the types of all data columns. A type should be specified in the list only once.
col_to_be_index: Name of the column you want as the new index. This name will not be a column in the result anymore
old_index_name: Name of the current index, if converted into a regular column in the result. If this is null, the current index will not be loaded into the result as a column.
|


SFUIStarMenu
-
This class represents an item of the star menu
Declaration
Swift
class SFUIStarMenuItem
-
The most common init you could do;author: Samuel GRAU :discussion: You should, if you want to code correctly with UIKit,
See moreDeclaration
Swift
override public init(frame: CGRect)
Parameters
frame
The frame you want to use at initialization time.
-
Undocumented
-
Undocumented
-
Undocumented


Issue: PRINT-CASE-BEHAVIORForum: X3J13 Letter Ballot
References: *PRINT-CASE* (X3J13/92-102, p22-65)
*PRINT-ESCAPE* (X3J13/92-102, p22-67)
Public review comment Pitman-8
Category: CLARIFICATION
Edit history: 21-Jun-93, Version 1 by Steele (based on text by Loosemore)
Status: Proposal CLARIFY passed 11-0 on letter ballot 93-304.
Problem Description:
This seems to be a case of poorly integrated cleanup issues.
We need to resolve ambiguities in the handling of *PRINT-CASE*.
The apparent contradictions are due to text from two proposals,
PRINT-CASE-PRINT-ESCAPE-INTERACTION:VERTICAL-BAR-RULE-NO-UPCASE and
READ-CASE-SENSITIVITY:READTABLE-KEYWORDS, that were previously adopted
by the committee. Going by the order of the votes on these issues,
READ-CASE-SENSITIVITY has priority over PRINT-CASE-PRINT-ESCAPE-INTERACTION,
which in turn has priority over any text derived from the base document.
Proposal (PRINT-CASE-BEHAVIOR:CLARIFY):
(a) This sentence on page 22-65:
Under no circumstance is
any character that is lowercase in the internal representation ever presented
as uppercase due to \varref{*print-case*}.
is quoted from the PRINT-CASE-PRINT-ESCAPE-INTERACTION proposal, which
was made obsolete by the subsequent adoption of the
READ-CASE-SENSITIVITY issue. We propose to remove this sentence.
(b) The text in section <IP_ADDRESS>.2 was derived from the
READ-CASE-SENSITIVITY proposal (which actually says "vertical-bar
syntax" rather than "escape syntax"). We propose to replace the phrase
When \term{escape} syntax is not being used,
with
When both \varref{*print-escape*} and \varref{*print-readably*} are
\term{false}, or the characters under consideration are not already
quoted specifically by \term{single escape} or \term{multiple escape}
syntax,
This choice is consistent with the decision from the
PRINT-CASE-PRINT-ESCAPE-INTERACTION proposal that the case in which
symbols print is affected by *PRINT-CASE* even when *PRINT-ESCAPE* is
false. It is also consistent with the Guy Steele's interpretation
in the second edition of "Common Lisp, the Language".
(c) This text from the first paragraph of section <IP_ADDRESS>
(but the case in which to print any uppercase characters in the
\term{name} is controlled by \thevariable{*print-case*}).
was derived from the base document and was made obsolete by the adoption
of the READ-CASE-SENSITIVITY proposal. We propose to replace this with
(but the case in which to print characters in the \term{name} is
controlled by \varref{*print-case*};
\seesection{ReadtableCasePrintEffect}).
Test Case:
Not provided.
Rationale:
We should better document the relationship between *PRINT-CASE* and
other printer control variables such as *PRINT-ESCAPE*.
Current Practice:
Not provided.
Cost to Implementors:
Probably relatively small.
Cost to Users:
None. This change doesn't affect anything already guaranteed to the user.
Cost of Non-Adoption:
Vagueness in the language specification.
Benefits:
Better program portability.
Editorial Impact:
Small. A few small, localized edits.
Aesthetics:
Mostly neutral.
Discussion:
This addresses comment Pitman #8.


Buyer and seller peace of mind starts with an honest discussion about the vehicle. To kickstart this, SureSale checks the vehicle’s title for over 75 different problems. Only vehicles with clean titles become SureSale Certified, check the results below.
We have inspected the vehicle, and provided you with a comprehensive condition report. We checked over 100 items, and documented any visible issues. Check the results below.
We are so confident in our selling process that we back it with a comprehensive Limited Warranty. This protection gives you the added assurance to know your SureSale vehicle is protected.
Rear Right
Scratch
3-5 Inches
Right Side
Road Rash on Hood
0-3 Inches
Rear Right
27Xx25/22
4/32
Rear Right
27Xx25/22
4/32
Rear Right
27Xx25/22
4/32
Rear Right
27Xx25/22
4/32


Truck Accident in Northern Philippines Kills 19 People, Leaves 22 Others Injured - Reports
MOSCOW (Sputnik) - A truck carrying passengers fell into a ravine in the Philippines' northern Apayao province, killing 19 people and leaving 22 others injured, media reported.
The Inquirer news outlet reported, citing police, that the accident took place in the municipality of Conner at around 07:00 p.m. (11:00 GMT) on Thursday.
According to Chief of Conner Police Capt. Manuel Canipas Jr., the truck's engine suddenly stopped while the vehicle was climbing up an uphill road in Barangay Karikitan. With the engine dead, the truck swiftly went backward and slid down into a 20-metre deep ravine. He added that, according to an initial investigation, the truck carried too many passengers which along with its weight caused the tragic accident.
Mylz Ginez, another official from Conner's Department of Public Works and Highways, pointed out that the truck driver was believed to have lost control of the steering wheel. Moreover, the vehicles' brakes failed to make it fall fell off a cliff in Conner.
The reports added that the majority of those killed were elderly people. They were on their way to the village of Lattut from the Kalinga province where they received financial support and seeds from the government.
Eleven of the injured people have been taken to Conner District Hospital and 11 others are being treated at Cagayan Valley Medical Center.
An investigation into the accident is underway.
The last similar incident took place in December 2017 when a bus crashed into another car, which claimed the lives of 20 of the 29 passengers.


{extend name="app/shop/view/base.html" /} {block name="resources"} {/block} {block name="main"}
0
0/0


setBaseUrl
QualitisNodeExecution
setCreateUser
QualitisSubmitRequest
setDescription
QualitisAddProjectRequest
QualitisUpdateProjectRequest
setExecutionUser
QualitisSubmitRequest
setGroupId
QualitisSubmitRequest
setPartition
QualitisSubmitRequest
setProjectId
QualitisDeleteProjectRequest
QualitisUpdateProjectRequest
setProjectName
QualitisAddProjectRequest
QualitisUpdateProjectRequest
setUsername
QualitisAddProjectRequest
QualitisDeleteProjectRequest
QualitisUpdateProjectRequest
state
QualitisNodeExecution
submit
QualitisNodeExecution


Last updated
Masch 17th, 2020
Codes Privacy Policy
Codes does not collect, store, or transmit any personal information.
Contact Information
If you have any questions regarding this privacy policy, you may email<EMAIL_ADDRESS>Last updated
Masch 17th, 2020
Codes does not collect, store, or transmit any personal information.
If you have any questions regarding this privacy policy, you may email info@ameba.co.


--- author: Colene Chow categories: app date: '2011-12-20 22:38:51' permalink: /2011/12/20/phonegap-for-windows-phone-getting-started/ slug: phonegap-for-windows-phone-getting-started status: publish title: 'PhoneGap for Windows Phone: Getting Started' type: post format: html tags: - Windows Phone - News ---
Yesterday, we announced the release of PhoneGap 1.3.0. This early holiday present included many improvements, new features and bug fixes across many platforms.
One of the most exciting parts of PhoneGap 1.3 is the full support of Windows Phone, including the full PhoneGap API and Windows Phone Getting Started Guide. Developers can also enjoy a selection of PhoneGap plug-ins that support social networks - including Facebook, LinkedIn, Windows Live and Twitter - and a solid integration into Visual Studio Express for Windows Phone.
"Building apps for Windows Phone requires the use of Visual Studio, and early on we chose to use C# as the development language for all native functionality," said Jesse MacFadyen, one of PhoneGap's core developers and main lead on bringing PhoneGap to Windows Phone. "Visual Studio is a very capable tool and the out of the box templates it gives you to make a Windows Phone app are very well documented, easy to understand, and a great help in getting started."
Read more about Jesse's experience on his blog and check out his two PhoneGap for Windows Phone videos below.
Part 1: Learn how to get up and running with PhoneGap 1.3.0 on Windows Phone:
Part 2: Get a deeper dive into PhoneGap 1.3 for Windows Phone
Learn more about Getting Started with PhoneGap for Windows Phone. Read Jesse's blog.